Awesome Filterable PortfolioWordPress extension · Brinidesigner
CVE-2022-35238
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauthenticated Plugin Settings Change vulnerability in Awesome Filterable Portfolio plugin <= 1.9.7 at WordPress.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Awesome Filterable Portfolio WordPress plugin versions 1.9.7 and below contains an unauthenticated settings change vulnerability, allowing remote attackers to modify plugin configuration without any authentication credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Awesome Filterable PortfolioWordPress extension
<= 1.9.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify plugin is installedCheck for the existence of the Awesome Filterable Portfolio plugin directory in wp-content/plugins/ (typically named awesome-filterable-portfolio or similar)Affected if The plugin directory exists in the WordPress plugins folder
-
Determine installed versionOpen the main plugin PHP file or readme.txt in the plugin directory and locate the version string in the plugin header commentAffected if Unable to locate version information in the plugin files
-
Compare version to affected rangeMatch the found version against the affected range: versions 1.9.7 and belowAffected if Installed version is 1.9.7 or lower (e.g., 1.9.7, 1.9.6, 1.9.5, etc.)
-
Confirm attack surface existsCheck if the plugin registers any AJAX actions (wp_ajax_ or wp_ajax_nopriv_ hooks) that handle settings changes without capability checksAffected if The plugin exposes settings-related AJAX endpoints accessible without authentication
If the plugin is installed and its version is 1.9.7 or lower, the environment is affected by this unauthenticated settings change vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the plugin to a version newer than 1.9.7. If no patched version is available, deactivate or remove the plugin until a fix is released.
Latest version available on wordpress.org (version > 1.9.7)
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find "Awesome Filterable Portfolio" in the plugin list
- Check if an update is available (if not, manually download latest version from wordpress.org)
- Click "Update Now" to upgrade the plugin to the latest available version
- Verify the update was successful and the plugin is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Awesome Filterable Portfolio
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35238 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-35238 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data