dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2023-25790

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Improper Authentication, Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in xtemos WoodMart allows Cross-Site Scripting (XSS).This issue affects WoodMart: from n/a through 7.0.4.

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 theme for WordPress versions through 7.0.4 contains a Cross-Site Scripting (XSS) vulnerability stemming from improper input neutralization during web page generation, combined with improper authentication issues that may allow attackers to inject malicious scripts into web pages viewed by other users.

MitigationUpdate the WoodMart theme to a version beyond 7.0.4 when available, or implement output encoding and input validation on all user-supplied data in the meantime.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Confirm WoodMart theme is installed
    Navigate to wp-content/themes/ in your WordPress installation directory and verify the woodmart folder exists, or check Appearance > Themes in WordPress admin panel for the WoodMart theme entry
    Affected if The WoodMart theme folder exists in wp-content/themes/ or is listed in WordPress admin themes
  2. Identify installed WoodMart version
    Open the style.css file located in wp-content/themes/woodmart/ and read the 'Version:' header in the file comments, or check the theme details in WordPress admin under Appearance > Themes > WoodMart
    Affected if The version displayed is 7.0.4 or any version number lower than 7.0.4
  3. Verify theme is active on the site
    In WordPress admin, go to Appearance > Themes and confirm WoodMart is the currently active theme, or check the active_theme option via wp-cli or database query
    Affected if WoodMart is the active theme in use on the WordPress site
  4. Inspect for suspicious script injections
    View the source code of publicly accessible pages on the site and search for unfamiliar JavaScript tags, malicious iframe elements, or script tags with encoded/obfuscated content in attributes like onload, onclick, or src
    Affected if Unexpected external script tags or malicious JavaScript is found embedded in site pages that users did not intentionally add

If the WoodMart theme version is 7.0.4 or lower and the theme is active on the WordPress site, the environment is affected by this XSS vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WoodMart theme to a version beyond 7.0.4 when available, or implement output encoding and input validation on all user-supplied data in the meantime.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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