WoodmartWordPress extension · Xtemos
CVE-2023-41872
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Xtemos WoodMart plugin <= 7.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 · moderate confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in Xtemos WoodMart WordPress theme plugin versions 7.2.4 and below. The vulnerability allows attackers to inject malicious JavaScript through unsanitized user input (likely a URL parameter) that gets reflected back in the HTTP response without proper output encoding.
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
WoodmartWordPress extension
<= 7.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
- 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.
-
Confirm WoodMart theme is installedCheck your WordPress installation for the WoodMart theme by examining wp-content/themes/woodmart/ directory or viewing the Themes section in WordPress admin panelAffected if WoodMart theme is present in the WordPress installation
-
Determine installed WoodMart versionCheck the style.css file in the WoodMart theme directory for the 'Version:' header, or query the WordPress database wp_options table for the 'woodmart_version' option valueAffected if Version is 7.2.4 or lower
-
Identify reflected URL parametersReview HTTP response headers and page source for any URL parameter values that appear verbatim in the response without HTML encoding. Common targets include search, category, or AJAX-related parametersAffected if URL parameters are reflected in the HTML response without proper encoding (e.g., < is shown as < instead of <)
-
Test for XSS via parameter reflectionCraft a request to the affected endpoint with a test payload such as ?param=<script>alert(1)</script> and inspect whether the script tags are rendered as-is in the responseAffected if The payload is reflected unescaped in the response and the browser would execute the injected JavaScript
A user is affected if WoodMart theme version 7.2.4 or below is installed AND unsanitized URL parameters are reflected in the HTTP response without HTML encoding.
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 to WoodMart version 7.3.0 or later which contains the security fix. As a temporary mitigation, consider deploying a WAF rule to filter malicious XSS payloads in incoming requests.
Fix this in Woodmart
Scoped from the published advisory
- Consultation1.0 h
- Implementation3.0 h
- Testing2.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 $2,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41872 — 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-41872 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