CVE-2026-109397: Thelia before 3.1.2 and 3.2.x before 3.2.1 File Upload RCE via Filename Trailing Space
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-10-12).
Weakness: Unrestricted Upload of File with Dangerous Type
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing high privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. 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
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 6 references on Exploit Observer
Live scores
- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.986
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Thelia | before 3.1.2 from 3.2.0 before 3.2.1 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 3.1.2, 3.2.1.
Vendor guidance:
- GitHub Security Advisory (GHSA-5524-qfxp-33v9) (vendor-advisory)
- https://github.com/thelia/thelia/commit/6b706f5cb96e6b12d890c6d16edb1c9d1fd8191a (patch)
- https://github.com/thelia/thelia/commit/b71258902b5dd278007d0f37ddad45f76d06d5bc (patch)
- Thelia 3.1.2 Release Notes (release-notes)
- Thelia 3.2.1 Release Notes (release-notes)
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-109397 Thelia - Unrestricted File Upload. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-109397 Thelia - Unrestricted File Upload"; flow:established,to_server; http.request_body; content:"filename"; nocase; content:".php|20 22|"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-109397; reference:url,https://www.exploit.observer/?keyword=CVE-2026-109397&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=thelia&match=exact; sid:1085804; rev:1;)
CVE-2026-109397.rules on GitHub
References
Vendor advisories and patches
- GitHub Security Advisory (GHSA-5524-qfxp-33v9) (vendor-advisory)
- https://github.com/thelia/thelia/commit/6b706f5cb96e6b12d890c6d16edb1c9d1fd8191a (patch)
- https://github.com/thelia/thelia/commit/b71258902b5dd278007d0f37ddad45f76d06d5bc (patch)
- Thelia 3.1.2 Release Notes (release-notes)
- Thelia 3.2.1 Release Notes (release-notes)
Technical analysis and advisories
- https://github.com/thelia/thelia/blob/3.2.0/core/lib/Thelia/Core/File/Service/FileProcessorService.php#L119-L160 (technical-description)
- VulnCheck Advisory: Thelia before 3.1.2 and 3.2.x before 3.2.1 File Upload RCE via Filename Trailing Space (third-party-advisory)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
