# CVE-2026-120248: Thelia before 3.1.1 Stored XSS via SVG Store Logo and Banner Uploads


- **Severity:** Medium 4.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-gvcv-hvpp-89gx, GHSA-xxr4-v6q3-9x28

## What is CVE-2026-120248?

CVE-2026-120248 is a medium-severity vulnerability in Thelia, published on 1 Nov 2026. 

### Official description

Thelia before 3.1.1 contains a stored cross-site scripting vulnerability that allows authenticated back-office administrators with store update permission to inject scripts by uploading unsanitized SVG logo_file or banner_file images. Attackers can upload an SVG with an onload payload served from /admin/store-media/logo or the public cache/images/store/ directory to execute scripts against visitors and higher-privileged administrators.

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

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


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

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

## Is CVE-2026-120248 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120248 is a medium-severity vulnerability in Thelia, published on 1 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120248 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-120248/ (Markdown: https://insights.sbomify.com/CVE-2026-120248/index.md)
```

## Sources

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

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