Blog Filter · Security record
Is Blog Filter safe?
No known vulnerability affects the current version (1.8.7). 3 issues were found in earlier versions and fixed, the latest disclosed on Feb 11, 2026.
Checked 1 day ago against the WPVulnerability database, for version 1.8.7.
How it’s looked after
- Last release
- Sep 1, 2026 (2 months ago)
- Releases in the last year
- 16
- Tested up to
- WordPress 7.1.4
- Support resolved
- 1 of 1 threads in two months
- Active installs
- 7K+
3 known vulnerabilities
- 3 medium
None affects the current version.
Disclosed each year
- 20231
- 20251
- 20261
Every known vulnerability in Blog Filter
Newest first, with any that affect the current version at the top.
Fixed in 1.7.7 · CVE-2026-39517 · Feb 11, 2026 · Wordfence
Fixed in 1.7.4 · CVE-2025-69033 · Dec 29, 2025 · Wordfence
Fixed in 1.5.4 · CVE-2023-5291 · Oct 3, 2023 · Wordfence
Questions about Blog Filter’s security
Is Blog Filter safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Blog Filter updated: most attacks target sites that haven’t updated.
Does Blog Filter have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 3 older issues, fixed in earlier versions, so keep Blog Filter up to date.
Is Blog Filter still maintained?
Yes. Its last release was 2 months ago. Its authors resolved 1 of the 1 support threads opened in the last two months.
Is Blog Filter compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.