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

CVE-2025-12903

HIGH · 7.5 CVSS v3.1 Published 2025-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Payment Plugins Braintree For WooCommerce plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the wc-braintree/v1/3ds/vaulted_nonce REST API endpoint in all versions up to, and including, 3.2.78. This is due to the endpoint being registered with permission_callback set to __return_true and processing user-supplied token IDs without verifying ownership or authentication. This makes it possible for unauthenticated attackers to retrieve payment method nonces for any stored payment token in the system, which can be used to create fraudulent transactions, charge customer credit cards, or attach payment methods to other subscriptions.

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 Braintree For WooCommerce plugin has an authorization bypass vulnerability where the REST API endpoint wc-braintree/v1/3ds/vaulted_nonce is registered with permission_callback set to __return_true, allowing unauthenticated access. The endpoint processes token IDs without verifying ownership or authentication, enabling attackers to retrieve payment method nonces for any stored token in the system.

MitigationUpdate to version 3.2.79 or later which adds proper capability checks and ownership verification to the vulnerable endpoint.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Verify Braintree For WooCommerce plugin is installed
    Check your WordPress plugins directory or WooCommerce plugins list for 'Braintree For WooCommerce' by visiting Plugins > Installed Plugins in WordPress admin, or inspect the file system for /wp-content/plugins/woocommerce-gateway-braintree/
    Affected if Plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Braintree For WooCommerce, and note the version number displayed under the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/woocommerce-gateway-braintree/woocommerce-gateway-braintree.php
    Affected if Version is less than 3.2.79 (e.g., 3.2.78, 3.2.77, etc.)
  3. Test vulnerable REST API endpoint accessibility
    Send an unauthenticated GET or POST request to your site's REST API endpoint: /wp-json/wc-braintree/v1/3ds/vaulted_nonce. Use curl or a browser developer tools to make the request. A response (even an error) indicates the endpoint exists and is reachable without authentication.
    Affected if Endpoint responds with any HTTP status (200, 400, 401, etc.) rather than being blocked, indicating permission_callback is set to __return_true

If the Braintree For WooCommerce plugin is installed with a version below 3.2.79 and the vulnerable REST API endpoint is accessible without authentication, the environment is affected by this authorization bypass.

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 version 3.2.79 or later which adds proper capability checks and ownership verification to the vulnerable endpoint.

Recommended fix High confidence

3.2.79 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Payment Plugins Braintree For WooCommerce' plugin
  4. Click 'Update Now' to install the latest version, or manually update to version 3.2.79 or higher
  5. Verify the update completed successfully

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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