# CVE-2026-128032: OpenMage magento-lts before 20.18.2 Payment Bypass via Free Payment Method


- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-pgqw-7723-22rc, GHSA-rmw8-7h79-p386

## What is CVE-2026-128032?

CVE-2026-128032 is a medium-severity vulnerability in OpenMage magento-lts, published on 13 Nov 2026. 

### Official description

OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 accepts the free (No Payment Information Required) payment method on orders with a non-zero total because the zero-total check runs only when payment data is imported. An API user with cart permissions can select free via cart_payment.method while the total is zero, raise it with cart_coupon.remove, and submit cart.order to place an unpaid full-price order.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow)

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


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

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

## Is CVE-2026-128032 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-128032 is a medium-severity vulnerability in OpenMage magento-lts, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128032 in the wild and no public exploit code.

Affected product: OpenMage magento-lts. 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-128032/ (Markdown: https://insights.sbomify.com/CVE-2026-128032/index.md)
```

## Sources

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

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