# CVE-2026-91076: Robokassa payment for WooCommerce < 1.9.0 - Unauthenticated Arbitrary Order Status Change to Failed

> Unauthenticated attackers can force any WooCommerce order to a failed state by sending unverified payment notifications, disrupting fulfillment.

- **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:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-jf7r-w4rc-fqxp

## What is CVE-2026-91076?

CVE-2026-91076 is a medium-severity missing authorization vulnerability in Unknown Robokassa payment gateway for Woocommerce, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Robokassa payment gateway for Woocommerce WordPress plugin before 1.9.0 does not verify the authenticity of an incoming payment-notification request before acting on the order named in it, allowing unauthenticated attackers to force any WooCommerce order into a failed state. Order identifiers are sequential, so every order in the shop can be taken out of the fulfilment queue one request at a time.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-91076 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91076 is a medium-severity missing authorization vulnerability in Unknown Robokassa payment gateway for Woocommerce, published on 14 Oct 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-91076 in the wild and no public exploit code.

Affected product: Unknown Robokassa payment gateway for Woocommerce. 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-91076/ (Markdown: https://insights.sbomify.com/CVE-2026-91076/index.md)
```

## Sources

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

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