# CVE-2026-15213: Welcart e-Commerce < 2.11.33 - Unauthenticated Payment Bypass via Forged Settlement Callback

> Unauthenticated attackers can forge settlement callbacks to mark unpaid orders as paid, bypassing payment verification in the Welcart e-Commerce plugin.

- **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:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-6p56-v4j4-jm3x

## What is CVE-2026-15213?

CVE-2026-15213 is a medium-severity vulnerability in Unknown Welcart e-Commerce, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Welcart e-Commerce WordPress plugin before 2.11.33 does not verify the authenticity of its convenience-store / bank-transfer settlement callback: an unauthenticated request can flip an order from unpaid to settled purely from an order number and a status flag, with no signature, amount, or origin check. Because these are pay-later methods, an attacker can mark their own unpaid order as settled and obtain fulfilment without paying.

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


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

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

## Is CVE-2026-15213 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15213 is a medium-severity vulnerability in Unknown Welcart e-Commerce, published on 12 Aug 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-15213 in the wild and no public exploit code.

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

## Sources

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

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