Awesome Filterable PortfolioWordPress extension · Brinidesigner
CVE-2022-40193
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 Stored Cross-Site Scripting (XSS) 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 · high confidenceAn unauthenticated stored XSS vulnerability exists in the Awesome Filterable Portfolio WordPress plugin (versions 1.9.7 and below). Attackers can inject malicious JavaScript payloads through plugin parameters that are stored in the database and executed when other users view affected pages.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 the plugin is installedNavigate to WordPress admin > Plugins and look for 'Awesome Filterable Portfolio' or 'Brinidesigner Awesome Filterable Portfolio' in the installed plugins listAffected if The plugin is not found in the plugins list, then not affected
-
Check the installed versionIn WordPress admin > Plugins, find the Awesome Filterable Portfolio plugin and check the version number displayed beneath the plugin nameAffected if The installed version is 1.9.7 or lower, indicating the vulnerable version
-
Confirm the plugin is activeIn WordPress admin > Plugins, verify the plugin status shows as 'Active'Affected if The plugin is active and running a vulnerable version, making exploitation possible
-
Inspect database for suspicious stored contentCheck WordPress posts/pages for portfolio items or shortcode outputs that may contain injected JavaScript; examine the wp_posts table for any unusual script tags or javascript: URIs in custom field values related to the pluginAffected if Malicious payloads are found stored in the database, confirming active exploitation
A user is affected if the Awesome Filterable Portfolio plugin is installed, active, and running version 1.9.7 or below.
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 Awesome Filterable Portfolio plugin to a version newer than 1.9.7, or if no update is available, disable and remove the plugin until a patched version is released.
Update to version 1.9.8 or later (latest available version)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Awesome Filterable Portfolio' in the list
- Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload it
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Awesome Filterable Portfolio
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40193 — 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-40193 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