# CVE-2026-112285: Thelia before 3.1.5 and 3.2.4 Coupon Usage Limit Bypass via Pay-Later Orders

> Authenticated users can bypass coupon usage limits by exploiting pay-later order logic, allowing unlimited discounts in Thelia e-commerce platforms.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-j67m-qx25-v22p, GHSA-pq5m-7g9w-ppg8

## What is CVE-2026-112285?

CVE-2026-112285 is a medium-severity vulnerability in Thelia, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Thelia before 3.1.5 and 3.2.x before 3.2.4 contains a business logic vulnerability that allows authenticated customers to bypass coupon usage limits because usage is counted only when orders become paid. Attackers can place multiple pay-later orders while a usage remains, or cancel paid orders to inflate max_usage, gaining unlimited discounts.

Weakness: CWE-837 (Improper Enforcement of a Single, Unique Action)

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


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

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

## Is CVE-2026-112285 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112285 is a medium-severity vulnerability in Thelia, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-112285 in the wild and no public exploit code.

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

## Sources

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

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