TYPO3 File manager extension: SQL injection in file search
Summary
The third-party TYPO3 extension "File manager" (ameos_filemanager) does not properly escape quote characters in its file search, so a crafted search term can change the database query. An attacker can read data from the TYPO3 database, and every searched field is affected. The vendor rates the issue as high severity; according to the vendor vector, no authentication is required, but whether the vulnerable search is reachable from the public internet on a given site must be verified.
Affected
- ameos/ameos_filemanager (TYPO3 extension "File manager") 0 to 3.1.2
- Versions below 3.1.3 are affected; the default configuration is unaffected according to the CVE record.
Fixed in
- Version 3.1.3 (available from the TYPO3 extension manager, Packagist and the TER download).
Workaround
- The vendor documents no workaround; its stated remedy is updating to 3.1.3.
- If patching is delayed: restrict or disable the search endpoint for anonymous users, review web application firewall rules for the search parameter, and ensure the TYPO3 database account follows least privilege.
Exploitation
- CISA SSVC (via ADP): exploitation none, automatable yes, technical impact partial.
- Not listed in the CISA KEV catalogue; HOL reports no known exploitation.
- No public proof of concept or exploit was found in the research. This is not confirmation of absence.
- VulDB shows a "0-Day" label without further detail, which could not be verified.
Our recommendation
- Inventory all TYPO3 installations and check for ameos/ameos_filemanager 3.1.2 or lower.
- Update to 3.1.3 and confirm the installed version afterwards.
- Until the update is done, restrict the search for anonymous users and review database and web logs for unusual search requests.
- Check whether the database data at risk includes personal data, as this may have GDPR and FADP implications.
- Re-check the NVD record, which is currently Deferred, and the TYPO3 advisory for changes.
- Scoring differs between sources (CVSS 4.0 8.7 vendor vector; VulDB 6.3), so prioritise patching based on the exposure of each site.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- TYPO3 security advisory TYPO3-EXT-SA-2026-034 typo3.org
- OpenCVE CVE-2026-112238 app.opencve.io
- VulDB 422724 vuldb.com
- HOL Guard CVE-2026-112238 hol.org
- Vulners CNNVD-2026-42450537 vulners.com
- ameos/ameos_filemanager on GitHub github.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 1 Nov 2026, 01:32.
Original description (NVD)
The file search of the extension builds its database conditions by wrapping the search term in quotes itself. Only the wildcard characters of the LIKE operator are escaped, quote characters are not. A crafted search term can therefore leave the intended string value and change the database query. This allows an attacker to read data from the database. The issue affects every searched field.
NVD references (1)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.