dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13930

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-19
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 Checkout Field Manager (Checkout Manager) for WooCommerce plugin for WordPress is vulnerable to authorization bypass in versions up to, and including, 7.8.5. This is due to the plugin not properly verifying that a user is authorized to delete an attachment combined with flawed guest order ownership validation. This makes it possible for unauthenticated attackers to delete attachments associated with guest orders using only the publicly available wooccm_upload nonce and attachment ID.

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 Checkout Field Manager for WooCommerce plugin fails to properly validate user authorization when deleting attachments. The vulnerability stems from the combination of a publicly exposed wooccm_upload nonce and flawed guest order ownership validation, allowing unauthenticated attackers to delete any attachment associated with guest orders by knowing only the nonce and attachment ID.

MitigationUpdate the plugin to version 7.8.6 or later. Until an update is available, implement web application firewall rules to block unauthorized attachment deletion requests and consider temporarily disabling the upload functionality.

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. Check the installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate 'Checkout Field Manager for WooCommerce', and compare the version number to 7.8.6
    Affected if The installed version is lower than 7.8.6
  2. Verify if upload fields are active in checkout
    Go to WooCommerce > Checkout Fields, or inspect the checkout page source, and determine if any file upload fields are enabled for customer use
    Affected if File upload fields are enabled and visible on the checkout form
  3. Confirm guest checkout is allowed
    Check WooCommerce > Settings > General for the 'Allow customers to place orders without an account' option, or review if guest order creation is permitted in the store
    Affected if Guest checkout is enabled and order creation without login is permitted
  4. Inspect for exposed wooccm_upload nonce
    View the HTML source of a checkout page and search for a hidden field or JavaScript variable containing 'wooccm_upload' to see if the nonce value is publicly exposed
    Affected if The wooccm_upload nonce is visible in the frontend source code without authentication

A user is affected if their installed plugin version is below 7.8.6, the upload functionality is enabled, guest checkout is permitted, and the wooccm_upload nonce is publicly exposed in the frontend.

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 the plugin to version 7.8.6 or later. Until an update is available, implement web application firewall rules to block unauthorized attachment deletion requests and consider temporarily disabling the upload functionality.

Recommended fix Moderate confidence

Upgrade to version 7.8.6 or later (the latest available version from the WordPress plugin repository)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Checkout Field Manager (Checkout Manager) for WooCommerce'
  4. If an update is available, click 'Update Now' to upgrade to the latest patched version
  5. After updating, verify the plugin is functioning correctly by testing the checkout process
  6. Confirm that attachment deletion functionality still works for authorized users
Caveat Standard minor version upgrade - review plugin settings after update to ensure configuration is intact

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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