Awesome Filterable Portfolio - Security Vulnerability (CVE-2022-35238)
CVE-2022-35238
Unauthenticated Plugin Settings Change vulnerability in Awesome Filterable Portfolio plugin
CVE-2022-35238
CVE-2022-35238
Unauthenticated Plugin Settings Change vulnerability in Awesome Filterable Portfolio plugin
CVE-2022-35238
Machine-generated threat intelligence
AI Updated 224 days ago
AI enriched 224 days ago (2026-04-11 20:30 UTC)
Unauthenticated Plugin Settings Change vulnerability in Awesome Filterable Portfolio plugin
Severity is MEDIUM (CVSS 6.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability is assessed as Medium based on low-bar exploit prerequisites.
Primary risk drivers: low-bar exploit prerequisites
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
AI risk score 62/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.
Patch promptly The consequence is significant even where an attacker needs a foothold first.
Update Awesome Filterable Portfolio to the latest available version.
Where the vendor has not published a fix yet, disable the plugin until they do.
No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.
Scan your site to see whether it runs Awesome Filterable Portfolio, and at which version.
Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.
You are affected if your site runs Awesome Filterable Portfolio. No account is needed to exploit this, so a public site is reachable by anyone.
Update Awesome Filterable Portfolio to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do.