# CVE-2026-84091: SUMIT Payment Gateway for WooCommerce < 4.0.0 - Unauthenticated Payment Confirmation Forgery via bit IPN

> Unauthenticated attackers can forge payment confirmations to mark orders as paid without completing payment, requiring plugin upgrade.

- **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:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-5gpw-3mxh-8583

## What is CVE-2026-84091?

CVE-2026-84091 is a medium-severity vulnerability in Unknown SUMIT Payment Gateway for WooCommerce, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SUMIT Payment Gateway for WooCommerce WordPress plugin before 4.0.0 does not verify with the payment provider that a payment notification is genuine before marking the corresponding order as paid, allowing unauthenticated users to mark a pending order paid without completing payment.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-84091 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84091 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84091 is a medium-severity vulnerability in Unknown SUMIT Payment Gateway for WooCommerce, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84091 exists.

Affected product: Unknown SUMIT 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-84091/ (Markdown: https://insights.sbomify.com/CVE-2026-84091/index.md)
```

## Sources

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

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