Portfolio PostWordPress extension · Themify
CVE-2022-32970
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 · uneditedAuth. (editor+) Stored Cross-Site Scripting (XSS) vulnerability in Themify Themify Portfolio Post plugin <= 1.2.4 versions.
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 confidenceAuthenticated users with editor privileges or higher can inject malicious JavaScript through the Themify Portfolio Post plugin's input fields. The stored XSS executes when other users view the portfolio content, allowing session hijacking, defacement, or credential theft.
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
Portfolio PostWordPress extension
<= 1.2.4CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Themify Portfolio Post plugin is installedNavigate to WordPress admin > Plugins and locate 'Themify Portfolio Post' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Identify the installed versionClick on the plugin name or view details to see the version number displayedAffected if The version listed is 1.2.4 or lower
-
Verify editor-level or higher user accounts existNavigate to WordPress admin > Users and review user roles; check if any accounts have Editor, Author, or Administrator privilegesAffected if There are users with Editor, Author, or Administrator roles who can access the plugin functionality
-
Confirm portfolio post functionality is accessibleCheck if the Themify Portfolio Post post type is active by visiting the portfolio section in the admin dashboard or viewing published portfolio content on the siteAffected if Portfolio posts are published and viewable on the frontend of the site
-
Check for unescaped content in portfolio postsView the HTML source of a portfolio post page using browser developer tools or view-source, looking for unsanitized script tags or event handlers in the post contentAffected if The rendered HTML contains raw script tags, javascript: URLs, or event handlers like onload, onerror without proper escaping
You are affected if Themify Portfolio Post version 1.2.4 or lower is installed and active on a WordPress site where users with Editor or higher privileges can create or view portfolio content.
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.
From vendor dataUpdate Themify Portfolio Post plugin to a version beyond 1.2.4. If no update is available, implement input sanitization and output escaping in the plugin code, or remove the plugin until a fix is released.
Fix this in Portfolio Post
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32970 — 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-32970 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