Security readout for executives and security teams
Plain-English summary
A flaw in the TYPO3 "Faceted Search" (ke_search) extension lets a trusted backend user with indexer configuration rights point the file indexer at directories outside its intended scope. That can expose file contents from elsewhere on the server through search results. The risk requires an insider or a compromised privileged account, so impact is meaningful but not broad.
Executive priority
Schedule as a routine patch cycle item for teams operating TYPO3 with ke_search. Not an emergency, but should be closed within the normal monthly maintenance window and paired with a review of who can edit indexer configurations.
Technical view
The file indexer in ke_search does not normalize the configured directory path, allowing path traversal sequences to reference arbitrary filesystem locations (CWE-22). CVSS 4.0 is 5.9 with attack vector Network, high privileges required, no user interaction, and high confidentiality impact but no integrity or availability impact. TYPO3 advisory TYPO3-EXT-SA-2026-011 lists affected version ranges starting at 0, 5.0.0, 6.0.0, and 7.0.0.
Likely exposure
TYPO3 sites running the ke_search (tpwd/ke_search) extension where backend editors or administrators can configure file indexer entries. Exposure is limited to environments that grant indexer configuration rights beyond the smallest trusted admin group.
Exploitation context
No KEV listing and no public exploitation reported in the source bundle. Exploitation requires an authenticated backend user with high privileges to modify indexer configuration, so risk is tied to insider misuse or compromise of a privileged account rather than opportunistic attack.
Researcher notes
CVSS 4.0 vector reflects PR:H and confidentiality-only impact, aligning with the requirement for a backend user with indexer configuration rights. CWE-22 path traversal stems from missing normalization of the configured directory. Affected version anchors in the bundle (0, 5.0.0, 6.0.0, 7.0.0) indicate multiple maintained branches; refer to the vendor advisory for exact fixed versions before validating remediation.
Mitigation direction
- Consult TYPO3 advisory TYPO3-EXT-SA-2026-011 and upgrade ke_search to the vendor-fixed release.
- Restrict backend permissions to modify indexer configurations to a minimal trusted group.
- Audit existing indexer configurations for suspicious directory paths or traversal sequences.
- Enforce strong authentication and MFA on TYPO3 backend administrator accounts.
- Monitor TYPO3 backend logs for changes to ke_search indexer settings.
Validation and detection
- Inventory TYPO3 sites and confirm which run tpwd/ke_search and at what version.
- Cross-check installed versions against fixed releases named in the TYPO3 advisory.
- Review backend user groups to identify which accounts hold indexer configuration rights.
- Inspect current indexer directory paths for values outside expected content roots.
- Verify post-upgrade that indexer paths are normalized and cannot resolve outside allowed roots.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-46724 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N——TYPO3Vulnerability scoring details
Base CVSS 4.0 score
5.9MediumVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://typo3.org/security/advisory/typo3-ext-sa-2026-011CVE reference, TYPO3 · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.