dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-9463

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Payments Plugin and Checkout Plugin for WooCommerce: Stripe, PayPal, Square, Authorize.net plugin for WordPress is vulnerable to time-based SQL Injection via the ‘order_by’ parameter in all versions up to, and including, 1.117.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Payments Plugin and Checkout Plugin for WooCommerce (Stripe, PayPal, Square, Authorize.net) is vulnerable to time-based SQL Injection via the 'order_by' parameter in versions up to 1.117.5. The vulnerability stems from insufficient escaping of user-supplied input combined with lack of prepared statements in the existing SQL query, allowing authenticated attackers with Subscriber-level access or higher to inject malicious SQL queries.

MitigationUpdate the plugin to version 1.117.6 or later. If a patch is unavailable, implement strict allowlist validation for the order_by parameter and refactor the SQL queries to use prepared statements with proper parameter binding.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify the installed plugin and version
    Check the WordPress plugin directory or database for 'Checkout Plugin for WooCommerce' or 'Payments Plugin for WooCommerce' and note the installed version number
    Affected if The plugin is installed and the version is 1.117.5 or lower
  2. Compare version to affected range
    Compare your installed version against 1.117.5 - versions 1.117.5 and below are affected, version 1.117.6 and later are not
    Affected if Installed version is 1.117.5 or lower (any version up to and including 1.117.5)
  3. Check if order_by parameter is accessible
    Inspect HTTP requests or logs for usage of the 'order_by' parameter in plugin endpoints, particularly in sorting functionality for payment/order listings
    Affected if The plugin processes user-supplied 'order_by' parameter without prepared statements (this is the vulnerable code path)
  4. Verify user role exposure
    Confirm that Subscriber-level or higher user accounts exist and can access the plugin's sorting functionality
    Affected if Authenticated users with Subscriber role or higher can trigger the vulnerable parameter

You are affected if the Payments or Checkout Plugin for WooCommerce is installed with version 1.117.5 or lower and processes the 'order_by' parameter from authenticated users.

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 1.117.6 or later. If a patch is unavailable, implement strict allowlist validation for the order_by parameter and refactor the SQL queries to use prepared statements with proper parameter binding.

Recommended fix Moderate confidence

Version 1.117.6 or latest stable release

  1. 1. Identify the exact plugin name from the WordPress admin dashboard under Plugins > Installed Plugins
  2. 2. Confirm the current installed version matches 1.117.5 or earlier
  3. 3. Before upgrading, backup the WordPress database and files
  4. 4. Navigate to Dashboard > Updates or go to Plugins > Add New > Upload (if using a premium version)
  5. 5. Update the plugin to the latest available version (1.117.6 or later)
  6. 6. Verify the update completed successfully
  7. 7. Test that the 'order_by' parameter in any affected functionality works correctly
Caveat Standard minor version update - unlikely to introduce breaking changes, but test in staging if possible

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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