WoodmartWordPress extension · Xtemos

CVE-2023-32500

HIGH · 8.8 CVSS v3.1 Published 2023-11-09
Fix available
A fix is available. Upgrade to 7.1.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in xtemos WoodMart - Multipurpose WooCommerce Theme <= 7.1.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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in xtemos WoodMart WooCommerce theme versions 7.1.1 and below allows attackers to trick authenticated administrators into performing unintended actions (such as modifying theme settings or site configuration) by exploiting the absence of anti-CSRF token validation on state-changing requests.

MitigationUpdate to WoodMart theme version 7.1.2 or later to receive the vendor patch. Additionally, implement anti-CSRF tokens (nonce validation) on all forms and AJAX actions that perform state-changing operations.

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
Affected:< 7.1.2

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WoodMart theme is installed
    Check for the existence of wp-content/themes/woodmart/ directory, or view installed themes in WordPress admin under Appearance > Themes
    Affected if WoodMart theme directory exists in the WordPress themes folder
  2. Determine installed WoodMart version
    Open the style.css file located in wp-content/themes/woodmart/ and locate the 'Version:' header, or view theme version in WordPress admin under Appearance > Themes > WoodMart Details
    Affected if Version read from style.css is below 7.1.2 or version cannot be determined
  3. Identify state-changing endpoints
    Review PHP files in wp-content/themes/woodmart/ that handle form submissions and AJAX requests, looking for functions that modify theme settings, site configuration, or user data
    Affected if State-changing endpoints exist in the theme and are accessible to authenticated administrators
  4. Check for anti-CSRF token validation
    Inspect the identified state-changing PHP handlers for presence of wp_verify_nonce, check_ajax_referer, or similar nonce validation functions before processing requests
    Affected if State-changing request handlers lack nonce verification logic

The environment is affected if WoodMart theme version is below 7.1.2 AND the theme contains state-changing request handlers that do not validate anti-CSRF tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.1.2 or later
Fixed in 7.1.2
Interim mitigation

Update to WoodMart theme version 7.1.2 or later to receive the vendor patch. Additionally, implement anti-CSRF tokens (nonce validation) on all forms and AJAX actions that perform state-changing operations.

Recommended fix High confidence

WoodMart theme version 7.1.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. Locate the WoodMart theme
  4. Click on the theme and select Update to version 7.1.2
  5. Alternatively, upload theme version 7.1.2 via Appearance > Themes > Add New > Upload Theme
  6. Verify the theme version is now 7.1.2 after update completion

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Woodmart Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32500 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32500 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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