dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-42725

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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
Authorization Bypass Through User-Controlled Key vulnerability in WP Wham Checkout Files Upload for WooCommerce checkout-files-upload-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Checkout Files Upload for WooCommerce: from n/a through <= 2.2.5.

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

Authorization bypass vulnerability in the WordPress plugin 'Checkout Files Upload for WooCommerce' (versions <= 2.2.5) allows attackers to manipulate user-controlled keys to bypass access control checks, potentially enabling unauthorized access to uploaded files or checkout functionality.

MitigationUpdate to a patched version when available; if no patch exists, implement proper authorization validation on all user-controlled parameters in the plugin's file upload handlers and restrict access to checkout file endpoints based on proper authentication and session validation.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

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 plugin installation
    Locate the 'Checkout Files Upload for WooCommerce' plugin in the WordPress plugins directory (wp-content/plugins/) or check via WordPress admin plugin list
    Affected if Plugin is present in the WordPress installation
  2. Determine installed version
    Open the main plugin PHP file or readme.txt and locate the Version header field; compare the version number against 2.2.5
    Affected if Installed version is 2.2.5 or lower
  3. Verify upload functionality is enabled
    Check WooCommerce plugin settings to confirm file upload during checkout is enabled; inspect the plugin configuration page for any active upload-related options
    Affected if Checkout file upload feature is enabled in plugin settings
  4. Test authorization on upload endpoint
    Attempt to access the plugin's file upload handler endpoint directly without valid authentication or session, manipulating user-controlled parameters (such as order ID or upload key) to see if access control can be bypassed
    Affected if Upload endpoint accepts requests without proper authorization validation on user-controlled parameters

User is affected if the plugin is installed with version 2.2.5 or lower and the checkout file upload feature is enabled, particularly if the upload endpoint can be accessed without proper authorization checks on user-controlled parameters.

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 to a patched version when available; if no patch exists, implement proper authorization validation on all user-controlled parameters in the plugin's file upload handlers and restrict access to checkout file endpoints based on proper authentication and session validation.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (vendor should confirm 2.2.6 or later contains the security fix)

  1. Check WordPress admin panel for available plugin updates for 'Checkout Files Upload for WooCommerce'
  2. Navigate to Plugins > All Plugins and verify if an update is available for the checkout-files-upload-woocommerce plugin
  3. If an update is available, update the plugin to the latest version available from the WordPress plugin repository
  4. After updating, verify the plugin version in Plugins > Installed Plugins to confirm the update was applied
  5. Test the file upload functionality in the WooCommerce checkout process to ensure the plugin still functions correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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