Woodmart ThemeWordPress extension · Xtemos
CVE-2023-32239
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. (subscriber+) Stored Cross-Site Scripting (XSS) vulnerability in xtemos WoodMart theme <= 7.2.1 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 · moderate confidenceAuthenticated stored XSS vulnerability in xtemos WoodMart theme allows subscribers to inject malicious JavaScript via theme settings fields. The vulnerability exists in versions 7.2.1 and below, where user input in certain theme options is not properly sanitized before being stored and rendered.
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
Woodmart ThemeWordPress extension
<= 7.2.1CVSS 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.
-
Identify WoodMart theme versionNavigate to WordPress admin > Appearance > Themes, locate the WoodMart theme, and view the theme details to find the installed version number. Alternatively, check the style.css file in the theme directory for the Version: field.Affected if The installed version is 7.2.1 or lower
-
Verify theme settings accessibilityCheck if the WordPress user role 'subscriber' can access theme settings panel (WoodMart > Theme Settings). Attempt to log in as a subscriber user and navigate to WoodMart > Theme Settings to confirm access.Affected if Subscriber-level users can access and modify theme settings
-
Inspect theme options for stored XSSNavigate to WoodMart > Theme Settings and examine any text input fields (such as custom code fields, labels, or text content fields). Check the database tables (typically wp_options) for theme settings values containing unsanitized HTML or script tags.Affected if Theme settings fields accept and store raw HTML/JavaScript without sanitization
You are affected if the installed WoodMart theme version is 7.2.1 or below AND subscriber-level users can access theme settings without proper output sanitization in place.
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 WoodMart theme to version 7.2.2 or later to receive the security patch. Alternatively, implement output sanitization on all theme settings input fields before rendering.
Woodmart Theme 7.2.2 or later
- 1. Update the Woodmart Theme to version 7.2.2 or later through the WordPress admin dashboard under Appearance > Themes, or download the latest version from the official Woodmart/ThemeForest source.
- 2. After updating, verify the theme version reflects 7.2.2 or higher in the WordPress admin.
- 3. Clear any caching mechanisms (page caches, CDN caches) to ensure the patched version is served.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Woodmart Theme
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32239 — 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-2023-32239 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