Filterable Portfolio · Security record
Is Filterable Portfolio safe?
One known vulnerability affects the current version (1.6.6), and it has no fix yet.
Checked 3 days ago against the WPVulnerability database, for version 1.6.6.
How it’s looked after
- Last release
- Apr 24, 2026 (6 months ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 7.0.8
- Active installs
- 1K+
1 known vulnerability
- 1 medium
1 affects the current version. 1 has no fix yet.
Every known vulnerability in Filterable Portfolio
Newest first, with any that affect the current version at the top.
Affects the current version · No fix yet · CVE-2024-4234 · Apr 26, 2024 · Wordfence
Questions about Filterable Portfolio’s security
Is Filterable Portfolio safe to use?
Yes: 1 known vulnerability affects version 1.6.6, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Filterable Portfolio have known security vulnerabilities?
Yes: 1 known vulnerability affects version 1.6.6, according to WPVulnerability’s database.
Is Filterable Portfolio still maintained?
Its last release was 6 months ago. No support threads were opened in the last two months.
Is Filterable Portfolio compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
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.