# CVE-2026-120205: Thelia before 3.1.0 Stored XSS via Coupon Condition Customer Name


- **Severity:** High 7.4 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Oct 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-pfq9-82gg-2grp, GHSA-r63g-6wfg-v5v9

## What is CVE-2026-120205?

CVE-2026-120205 is a high-severity vulnerability in Thelia, published on 31 Oct 2026. 

### Official description

Thelia before 3.1.0 contains a stored cross-site scripting vulnerability in ForSomeCustomers::getSummary() that allows unauthenticated attackers to inject scripts via unescaped customer names. Attackers can register with a script payload as their name that executes when administrators view related coupons, stealing CSRF tokens to create administrator accounts.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-120205 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120205 is a high-severity vulnerability in Thelia, published on 31 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120205 exists.

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

## Sources

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

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