dbcve.org
WoodmartWordPress extension · Xtemos

CVE-2023-32242

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-21
Fix available
A fix is available. Upgrade to 1.0.37 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Deserialization of Untrusted Data vulnerability in xtemos WoodMart - Multipurpose WooCommerce Theme.This issue affects WoodMart - Multipurpose WooCommerce Theme: from n/a through 1.0.36.

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

The WoodMart WooCommerce theme versions up to 1.0.36 contain a deserialization vulnerability that could allow an attacker to execute arbitrary code by processing untrusted serialized data. This type of vulnerability is particularly dangerous as it can lead to complete site compromise.

MitigationUpdate the WoodMart theme to a version newer than 1.0.36. If immediate updating is not feasible, consider disabling the theme or restricting access to any endpoints that handle serialized data until the patch can be applied.

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:< 1.0.37

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 the WordPress themes directory or wp-admin appearance > themes to confirm the Xtemos Woodmart theme is present on the site.
    Affected if The theme is installed and active on the WordPress site.
  2. Identify the installed WoodMart version
    Locate the style.css file within the WoodMart theme folder (typically /wp-content/themes/woodmart/) and read the Version header, or check the theme information in WordPress admin under Appearance > Themes.
    Affected if The version number found is less than 1.0.37 (for example: 1.0.36, 1.0.35, etc.).
  3. Check for AJAX or data processing endpoints
    Review the theme files for PHP files that handle serialized data, particularly in includes/ or framework/ directories, or check the site for any custom AJAX handlers that may accept serialized input via $_POST, $_GET, or file uploads.
    Affected if The theme contains endpoints or functions that process untrusted serialized data and these are accessible on the site.
  4. Confirm the deserialization vulnerability condition
    Examine whether the theme processes serialized data from user input without sanitization, or review server access logs for suspicious requests to theme AJAX endpoints containing serialized payloads.
    Affected if The vulnerable code path that handles deserialization of untrusted data is exposed and reachable.

The site is affected if the WoodMart theme version is below 1.0.37 and the theme is active with accessible endpoints that process serialized data.

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 1.0.37 or later
Fixed in 1.0.37
Interim mitigation

Update the WoodMart theme to a version newer than 1.0.36. If immediate updating is not feasible, consider disabling the theme or restricting access to any endpoints that handle serialized data until the patch can be applied.

Recommended fix High confidence

WoodMart theme version 1.0.37

  1. Update the WoodMart theme to version 1.0.37 or later via the WordPress dashboard (Appearance > Themes) or via the theme vendor's update mechanism
  2. Verify the update was successful by checking the theme version in Appearance > Themes
  3. If using a child theme, ensure it remains compatible with the updated parent theme
  4. Test critical WooCommerce functionality (cart, checkout, product display) after the update
  5. Ensure all other WordPress plugins and core are up to date as a security best practice

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

Fix this in Woodmart Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32242 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-32242 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