dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-9028

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-09
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 6 weeks old

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 CorvusPay WooCommerce Payment Gateway plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.7.4. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to cancel any WooCommerce order placed via the CorvusPay payment method by supplying an arbitrary order number to the /wp-json/corvuspay/cancel/ REST endpoint.

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 CorvusPay WooCommerce Payment Gateway plugin exposes a REST API endpoint at /wp-json/corvuspay/cancel/ that fails to verify user authorization before processing order cancellation requests. An unauthenticated attacker can cancel arbitrary orders by simply providing an order number to this endpoint, allowing them to disrupt legitimate transactions without any authentication or ownership verification.

MitigationUpdate the CorvusPay WooCommerce Payment Gateway plugin to version 2.7.5 or later, which should include proper authorization checks requiring user authentication and ownership verification before allowing order cancellation.

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 CorvusPay plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'CorvusPay WooCommerce Payment Gateway' or check the plugin files in wp-content/plugins/ for a corvuspay directory
    Affected if The plugin is installed and active in WordPress
  2. Check installed plugin version
    In WordPress admin plugins list, view the plugin details to see the version number, or read the main plugin file header in wp-content/plugins/corvuspay/includes/main.php or similar
    Affected if Version is lower than 2.7.5 or cannot be determined (assumed vulnerable)
  3. Confirm vulnerable endpoint exists
    Make a GET or POST request to /wp-json/corvuspay/cancel/ on the WordPress site and verify the endpoint responds (check for 200 or 400 status rather than 404)
    Affected if The endpoint responds with a valid API response (not 404 Not Found)
  4. Test for authorization bypass
    Send a request to /wp-json/corvispay/cancel/ with an arbitrary order_id parameter (e.g., ?order_id=123) without providing any authentication credentials (no cookies, no Authorization header)
    Affected if The request does not return 401 Unauthorized or 403 Forbidden error, indicating the endpoint processes requests without authentication

User is affected if the CorvusPay WooCommerce Payment Gateway plugin is installed with a version below 2.7.5 (or unknown) AND the /wp-json/corvuspay/cancel/ endpoint is accessible without 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 the CorvusPay WooCommerce Payment Gateway plugin to version 2.7.5 or later, which should include proper authorization checks requiring user authentication and ownership verification before allowing order cancellation.

Recommended fix Moderate confidence

CorvusPay WooCommerce Payment Gateway version 2.7.5 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'CorvusPay WooCommerce Payment Gateway' plugin
  4. Check the current version number (should be 2.7.4 or earlier)
  5. Update the plugin to the latest available version (2.7.5 or later)

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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