dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-14294

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 Razorpay for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the getCouponList() function in all versions up to, and including, 4.7.8. This is due to the checkAuthCredentials() permission callback always returning true, providing no actual authentication. This makes it possible for unauthenticated attackers to modify the billing and shipping contact information (email and phone) of any WooCommerce order by knowing or guessing the order 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 · high confidence

The Razorpay for WooCommerce plugin has a REST API endpoint with getCouponList() function whose checkAuthCredentials() permission callback always returns true, providing no authentication. This allows unauthenticated attackers to modify billing and shipping contact information (email, phone) of any WooCommerce order by knowing or guessing the order ID.

MitigationUpgrade to version 4.7.9 or later which implements proper capability checking on the affected REST API endpoint, or disable the plugin until the patch can be applied.

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. Verify Razorpay for WooCommerce is installed
    Navigate to WordPress admin > Plugins and confirm 'Razorpay for WooCommerce' appears in the installed plugins list, or check the filesystem at wp-content/plugins/ for a razorpay-woocommerce directory
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    In WordPress admin > Plugins, click on the Razorpay for WooCommerce plugin to view its version, or read the version from the plugin's main PHP file header in wp-content/plugins/razorpay-woocommerce/
    Affected if The version is lower than 4.7.9 (e.g., 4.7.8, 4.7.7, etc.)
  3. Identify the vulnerable REST API endpoint
    Locate the plugin file containing the getCouponList() function, typically in includes/class-razorpay-api.php or similar within the plugin directory, and identify the associated REST route (usually /razorpay/v1/coupons or similar)
    Affected if The getCouponList() function exists in the plugin code and is registered as a REST API endpoint
  4. Verify the vulnerable permission callback
    Examine the REST route registration code for the coupon endpoint and locate the checkAuthCredentials() permission callback function - confirm it returns true without performing any actual capability or authentication checks
    Affected if checkAuthCredentials() unconditionally returns true or has no authentication logic
  5. Test unauthenticated access to the endpoint
    Send a GET or POST request to the plugin's REST API endpoint (e.g., /wp-json/razorpay/v1/coupons) using a tool like curl or browser DevTools without providing any authentication credentials
    Affected if The endpoint returns a valid response (not a 401/403 authentication error)
  6. Confirm order modification is possible
    Using an HTTP client, send a request to modify billing/shipping contact fields on a known WooCommerce order ID via the affected endpoint without authentication
    Affected if The request succeeds and the order contact information is modified without requiring authentication

You are affected if Razorpay for WooCommerce version lower than 4.7.9 is installed AND the checkAuthCredentials() callback returns true unconditionally, allowing unauthenticated modification of order contact details via the REST API endpoint.

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

Upgrade to version 4.7.9 or later which implements proper capability checking on the affected REST API endpoint, or disable the plugin until the patch can be applied.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version higher than 4.7.8)

  1. Check the WordPress plugin repository or WooCommerce settings for the currently installed version of Razorpay for WooCommerce
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the Razorpay for WooCommerce plugin
  4. If an update is available, update to the latest version available in the WordPress plugin repository
  5. After updating, verify that the plugin is functioning correctly by placing a test order
  6. Confirm that the checkAuthCredentials() function now properly validates user permissions

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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