CVE-2026-46724
Path Traversal in File Indexer Configuration
Publication date: 2026-05-19
Last updated on: 2026-05-19
Assigner: TYPO3
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| typo3 | faceted_search | to 7.0.1 (exc) |
| typo3 | faceted_search | From 6.0.0 (inc) to 6.6.0 (inc) |
| typo3 | faceted_search | to 5.6.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs because the file indexer does not normalize the configured directory path. As a result, a backend user who has permission to edit indexer configurations can exploit path traversal sequences to index documents from arbitrary locations on the server's file system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows backend users with permission to edit indexer configurations to perform path traversal attacks, enabling them to index documents from arbitrary locations on the server file system. This can lead to unauthorized access and indexing of sensitive or confidential data.
Such unauthorized access and potential exposure of sensitive information could negatively impact compliance with data protection standards and regulations like GDPR and HIPAA, which require strict controls on access to personal and sensitive data.
Organizations using the affected TYPO3 extension should update to fixed versions and follow security best practices to mitigate risks and maintain compliance.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves the TYPO3 Faceted Search extension's file indexer allowing path traversal due to lack of directory path normalization. Detection involves checking if the affected versions of the extension are in use and if backend users have permissions to edit indexer configurations.
To detect potential exploitation or presence of this vulnerability, you can:
- Check the installed version of the TYPO3 Faceted Search extension to see if it matches the vulnerable versions (7.0.0, 6.0.0 to 6.6.0, and 5.6.1 and below).
- Review backend user permissions to identify users with indexer configuration editing rights.
- Audit logs or monitoring tools for unusual indexing activity or attempts to index files outside the intended directories.
Specific commands depend on your environment, but examples include:
- On the TYPO3 server, use the command to check installed extension versions: `typo3 extension:list | grep faceted_search`
- Check file system access logs or web server logs for suspicious requests or indexing operations targeting unexpected file paths.
- Use TYPO3 backend user management commands or interface to list users with indexer configuration permissions.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the TYPO3 Faceted Search extension to a fixed version where the vulnerability is addressed.
- Update the extension to version 7.0.1, 6.6.1, or 5.6.2 or later using the TYPO3 extension manager, Packagist, or the official extension download page.
- Restrict backend user permissions to limit who can edit indexer configurations.
- Follow TYPO3 Security Guide recommendations and subscribe to the typo3-announce mailing list for ongoing updates.
How can this vulnerability impact me? :
The vulnerability allows a privileged backend user to access and index files from any location on the server file system, potentially exposing sensitive or unauthorized data. This could lead to information disclosure or unauthorized data access within the system.