# CVE-2026-109397: Thelia before 3.1.2 and 3.2.x before 3.2.1 File Upload RCE via Filename Trailing Space

> Authenticated back-office users can upload PHP files by appending trailing spaces to filenames, leading to remote code execution on the web server.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-5524-qfxp-33v9, GHSA-hjxm-gpw4-w4q7

## What is CVE-2026-109397?

CVE-2026-109397 is a high-severity vulnerability in Thelia, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Thelia before 3.1.2 and 3.2.x before 3.2.1 contains an unrestricted file upload vulnerability that allows authenticated back-office users to upload PHP files by appending a trailing space to filenames. FileProcessorService validates the raw filename but FileManager::sanitizeFileName() strips the space, storing an executable .php file under public/cache/documents/ for code execution as the web server user.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-109397 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109397 is a high-severity vulnerability in Thelia, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109397 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-109397/ (Markdown: https://insights.sbomify.com/CVE-2026-109397/index.md)
```

## Sources

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

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