dbcve.org
WoodmartWordPress extension · Xtemos

CVE-2025-6746

HIGH · 8.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 8.2.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
The WoodMart plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 8.2.3 via the 'layout' attribute. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php files can be uploaded and included.

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 plugin suffers from a Local File Inclusion (LFI) vulnerability via the 'layout' attribute, allowing authenticated users with Contributor-level access or higher to include and execute arbitrary .php files on the server. This enables arbitrary PHP code execution, which can be leveraged to bypass access controls, exfiltrate data, or achieve full server compromise.

MitigationUpdate WoodMart plugin to version 8.2.4 or later to patch the LFI vulnerability. Until patched, immediately review and restrict user accounts with Contributor-level permissions to minimize the attack surface.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 installation
    Check your WordPress installation for the WoodMart theme/plugin. In wp-content/themes/ or wp-content/plugins/, locate the woodmart folder and examine the style.css or index.php file to find the version number.
    Affected if The version displayed is lower than 8.2.4 (e.g., 8.2.3, 8.2.0, etc.)
  2. Confirm WordPress user roles
    In the WordPress admin dashboard, navigate to Users > All Users and review the role assigned to each account. Look for accounts with Contributor role or higher (Contributor, Author, Editor, Administrator).
    Affected if There is at least one user account with Contributor-level access or above.
  3. Inspect layout template usage
    Search theme template files (typically in wp-content/themes/woodmart/framework/templates/) for references to the 'layout' parameter being used in include/require statements, or monitor HTTP requests to the site for 'layout=' query parameters.
    Affected if The 'layout' attribute is used in template includes and is user-controllable via URL parameters.
  4. Review server access logs
    Examine web server access logs (Apache/nginx) for requests containing 'layout=' parameter pointing to .php files, such as ?layout=../../../../etc/passwd or ?layout=somefile.php.
    Affected if Any logged requests with manipulated 'layout' parameters are found in the logs.

Your environment is affected if WoodMart version is below 8.2.4 AND at least one user with Contributor-level or higher access exists on the WordPress site.

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 plugin to version 8.2.4 or later to patch the LFI vulnerability. Until patched, immediately review and restrict user accounts with Contributor-level permissions to minimize the attack surface.

Recommended fix High confidence

Woodmart theme version 8.2.4

  1. Create a complete backup of your WordPress site (database and files) before making any changes
  2. Update the WoodMart theme to version 8.2.4 or later through WordPress admin (Appearance > Themes) or your hosting control panel
  3. Verify the update was successful by checking the theme version in Appearance > Themes
  4. Review user accounts for any unauthorized new users with Contributor or higher roles
  5. Scan the wp-content/uploads and wp-content/plugins directories for any suspicious .php files that may have been uploaded
  6. Clear all WordPress caches if caching plugins are in use
  7. Monitor access logs for any unusual requests to the 'layout' parameter

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

Fix this in Woodmart Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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