dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-9284

HIGH · 8.2 CVSS v3.1 Published 2026-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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 WooCommerce PayPal Payments plugin for WordPress is vulnerable to unauthorized order manipulation and information disclosure due to missing authorization checks on the `ppc-create-order` and `ppc-get-order` WC-AJAX endpoints in all versions up to, and including, 4.0.1. The `ppc-create-order` endpoint accepts an arbitrary WooCommerce order ID in the `pay-now` context without validating order ownership, allowing attackers to create PayPal orders for any WC order and write PayPal metadata to it. The `ppc-get-order` endpoint returns full PayPal order details for any PayPal order ID without binding to the requester's session. This makes it possible for unauthenticated attackers to chain these endpoints to manipulate other customers' order payment flows and exfiltrate sensitive order details (payer information, shipping data) by creating a PayPal order for a victim's WC order and then retrieving the PayPal order data.

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 WooCommerce PayPal Payments plugin lacks authorization checks on two AJAX endpoints (ppc-create-order and ppc-get-order). Attackers can create PayPal orders for arbitrary WooCommerce orders without ownership validation, then retrieve full PayPal order details including payer information and shipping data by chaining these endpoints. This IDOR vulnerability allows unauthenticated users to manipulate any order and exfiltrate sensitive customer data.

MitigationUpdate to version 4.0.2 or later which includes proper authorization validation on the affected AJAX endpoints. Until patched, consider restricting access to these endpoints or implementing additional access controls at the web server level.

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Confirm WooCommerce PayPal Payments plugin is installed
    Navigate to WordPress admin > Plugins and verify 'WooCommerce PayPal Payments' appears in the installed plugins list, or inspect the plugin directory at /wp-content/plugins/woocommerce-paypal-payments/
    Affected if The plugin is installed and active in WordPress
  2. Identify the installed plugin version
    In WordPress admin > Plugins, click on the plugin to view details and read the installed version number, or check the main plugin file (e.g., woocommerce-paypal-payments.php) for the 'Version:' header comment
    Affected if The installed version is lower than 4.0.2 (vulnerable versions: 1.x, 2.x, 3.x before 3.x.x) or cannot be determined
  3. Verify the vulnerable AJAX endpoints are accessible
    Send a GET request to yoursite.com/?wc-ajax=ppc-get-order with a test order ID parameter (e.g., ?order_id=1) using a tool like curl or Burp, without providing authentication cookies
    Affected if The endpoint responds with HTTP 200 and returns PayPal order data or JSON structure without requiring login credentials
  4. Test order manipulation capability
    Send a POST request to yoursite.com/?wc-ajax=ppc-create-order with a valid but unrelated WooCommerce order ID in the request body (e.g., order_id=999) without authentication
    Affected if The request succeeds and creates a PayPal order bound to the arbitrary order ID, returning order details without authorization validation

You are affected if the WooCommerce PayPal Payments plugin is installed with a version below 4.0.2 AND the ppc-create-order or ppc-get-order AJAX endpoints respond without requiring WordPress/WooCommerce session authentication.

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 4.0.2 or later which includes proper authorization validation on the affected AJAX endpoints. Until patched, consider restricting access to these endpoints or implementing additional access controls at the web server level.

Recommended fix Moderate confidence

4.0.2 or later (latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WooCommerce PayPal Payments plugin
  4. Check the current version (should be 4.0.1 or below if vulnerable)
  5. If an update is available, click 'Update Now' to install the latest version
  6. Alternatively, navigate to Dashboard > Updates and update the plugin from there
  7. After updating, verify the plugin version is newer than 4.0.1

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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