dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-8097

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-26
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
The WoodMart theme for WordPress is vulnerable to Improper Input Validation in all versions up to, and including, 8.2.6. This is due to insufficient validation of the qty parameter in the woodmart_update_cart_item function. This makes it possible for unauthenticated attackers to manipulate cart quantities using fractional values, allowing them to obtain products for free by setting extremely small quantities (e.g., 0.00001) that round cart totals to $0.00, effectively bypassing payment requirements and allowing unauthorized acquisition of virtual or downloadable products.

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 up to version 8.2.6 fails to properly validate the qty parameter in the woodmart_update_cart_item function. Attackers can submit fractional quantities (e.g., 0.00001) that cause cart totals to round down to $0.00, enabling free acquisition of virtual or downloadable products without payment.

MitigationUpdate WoodMart theme to version 8.2.7 or later which contains the patched input validation for the cart quantity parameter.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm WoodMart theme is installed
    Check the active WordPress theme via WordPress admin under Appearance > Themes, or inspect wp-content/themes/woodmart/style.css for the theme header
    Affected if WoodMart theme is the active theme
  2. Identify the installed WoodMart version
    Review the version number in the theme header of wp-content/themes/woodmart/style.css or check via WordPress admin theme details
    Affected if Version is 8.2.6 or lower
  3. Verify WooCommerce is active
    Check WordPress admin under Plugins > Installed Plugins to confirm WooCommerce is installed and activated
    Affected if WooCommerce is active and the cart functionality is in use
  4. Confirm the vulnerable function exists
    Inspect the file wp-content/themes/woodmart/framework/classes/ cart.php (or similar cart-related file) for the function woodmart_update_cart_item and verify it accepts the qty parameter without proper validation
    Affected if The function processes qty input without validating for safe numeric values

A user is affected if they have WoodMart theme version 8.2.6 or lower active on a WordPress site with WooCommerce enabled, where the cart quantity update function processes unvalidated fractional input.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WoodMart theme to version 8.2.7 or later which contains the patched input validation for the cart quantity parameter.

Recommended fix Moderate confidence

WoodMart theme version 8.2.7 or later

  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 number of the theme
  5. 5. If the installed version is 8.2.6 or lower, update to version 8.2.7 or later
  6. 6. Alternatively, navigate to ThemeForest account > Downloads > WoodMart theme and download the latest version
  7. 7. Upload and install the updated theme, or use the WordPress theme update mechanism
  8. 8. Verify the update was successful by checking the theme version
Caveat Review theme changelog for any potential compatibility issues with child themes or customizations before updating

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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