# CVE-2026-92996: Verge3D 4.1.0 - 4.13.0 - Unauthenticated Payment Bypass via v3d_payment_done

> Unauthenticated attackers can bypass payment verification in Verge3D WordPress plugin to mark any order as paid without actual payment.

- **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:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-h272-7wqm-px5x

## What is CVE-2026-92996?

CVE-2026-92996 is a medium-severity vulnerability in Unknown Verge3D Publishing and E-Commerce, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Verge3D WordPress plugin from 4.1.0 through 4.13.0 does not verify with the payment provider that a payment was actually made, and does not check order ownership, allowing unauthenticated users to mark any order as paid.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-92996 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92996 is a medium-severity vulnerability in Unknown Verge3D Publishing and E-Commerce, published on 28 Sep 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-92996 in the wild and no public exploit code.

Affected product: Unknown Verge3D Publishing and E-Commerce. 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-92996/ (Markdown: https://insights.sbomify.com/CVE-2026-92996/index.md)
```

## Sources

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

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