# CVE-2026-9028: Missing authorization in CorvusPay WooCommerce Payment Gateway

> Unauthenticated attackers can cancel arbitrary WooCommerce orders via the CorvusPay payment gateway plugin by exploiting missing authorization checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-pqfh-v7pq-gjhm

## What is CVE-2026-9028?

CVE-2026-9028 is a medium-severity missing authorization vulnerability in corvusinfo CorvusPay WooCommerce Payment Gateway, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-9028?


## How do I fix CVE-2026-9028?

No fix has been published for CVE-2026-9028 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9028 being exploited?

There is no known exploitation of CVE-2026-9028 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9028 and fix it if it is affected.

What it is: CVE-2026-9028 is a medium-severity missing authorization vulnerability in corvusinfo CorvusPay WooCommerce Payment Gateway, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9028 in the wild and no public exploit code.

Affected product: corvusinfo CorvusPay WooCommerce Payment Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9028/ (Markdown: https://insights.sbomify.com/CVE-2026-9028/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9028
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9028
- OSV: https://osv.dev/vulnerability/CVE-2026-9028

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9028/
Summaries are generated and may contain mistakes; the official description above is the record.