dbcve.org
WoodmartWordPress extension · Xtemos

CVE-2025-6743

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 8.2.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The Woodmart theme for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'multiple_markers' attribute in all versions up to, and including, 8.2.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The Woodmart WordPress theme lacks proper input sanitization and output escaping on the 'multiple_markers' attribute, allowing authenticated users with contributor-level access or higher to inject malicious JavaScript that persists on affected pages and executes when other users view those pages.

MitigationUpdate Woodmart theme to version 8.2.4 or later, which contains proper sanitization and escaping for the multiple_markers attribute. Until updated, restrict contributor-level user permissions and audit existing content for suspicious script injections.

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

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

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

  1. Identify Woodmart theme installation
    Check your WordPress installation for the Xtemos Woodmart theme. In WordPress admin, go to Appearance > Themes. Alternatively, inspect the theme directory (wp-content/themes/woodmart) for the style.css file which contains the theme version header.
    Affected if The Woodmart theme is installed and active.
  2. Determine installed theme version
    Open the theme's style.css file (wp-content/themes/woodmart/style.css) and locate the 'Version:' header in the theme comments, or check via WordPress admin theme details panel.
    Affected if The version number is lower than 8.2.4 (e.g., 8.2.3, 8.2.0, 7.x.x, etc.).
  3. Identify use of map/marker features
    Review pages, posts, and custom post types (such as woodmart slider or woodmart portfolio) for elements using the 'multiple markers' or 'map' functionality. These are typically added via the WPBakery page builder or Elementor when Woodmart is installed.
    Affected if Content contains map elements with the multiple_markers attribute configured.
  4. Inspect content for injected scripts
    Examine the HTML source of pages using map/marker elements. Look for unexpected <script> tags, event handlers (onload, onerror, onmouseover), or javascript: URLs within the multiple_markers attribute values. Use browser developer tools or search the database for patterns like 'script' or 'javascript:' within map-related content.
    Affected if Malicious script tags or event handlers are present in the HTML output of map elements.
  5. Audit user accounts with contributor access
    In WordPress admin, go to Users > All Users and review the list for accounts with Contributor, Author, Editor, or Administrator roles. These users have sufficient permissions to create or edit content containing the vulnerable attribute.
    Affected if There are user accounts with Contributor-level access or higher who have permission to edit content.

Your environment is affected if the Woodmart theme version is below 8.2.4 AND you have content using map elements with the multiple_markers attribute AND you have users with contributor-level permissions who can edit that content.

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

Update Woodmart theme to version 8.2.4 or later, which contains proper sanitization and escaping for the multiple_markers attribute. Until updated, restrict contributor-level user permissions and audit existing content for suspicious script injections.

Recommended fix High confidence

Woodmart theme version 8.2.4

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the Woodmart theme
  4. 4. Check the current version to confirm it's below 8.2.4
  5. 5. Update the Woodmart theme to version 8.2.4 or later
  6. 6. Verify the update was successful by checking the theme version

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 / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6743 — 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-2025-6743 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