CVE-2026-46723: TYPO3 Extension "Faceted Search" · Resource Exposure
Affects TYPO3 Extension "Faceted Search"Source CVE Database V5
Not known to be exploited · CVSS 5.9 Medium · fixed in 7.0.1 : update TYPO3 Extension "Faceted Search" when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7.0.1, 6.6.1, 5.6.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Extension "Faceted Search" and tpwd/ke_search to 7.0.1, 6.6.1 or 5.6.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TYPO3Extension "Faceted Search" | Affected
| Fixed in
|
| TYPO3Extension "Faceted Search" | Affected
| Fixed in
|
| TYPO3Extension "Faceted Search" | Affected
| Fixed in
|
Packagisttpwd/ke_searchpkg:composer/tpwd/ke_searchOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict backend user permissions to only those necessary and carefully control who can edit indexer configurations to prevent exploitation of this vulnerability.
Description
CVE-2026-46723 is a medium severity vulnerability in the TYPO3 Extension "Faceted Search". It involves the additional_tables configuration of the page and tt_content indexers, which accepts arbitrary table and field names. This allows a backend user with permission to edit indexer configurations to copy sensitive data from internal TYPO3 tables into the search index, potentially exposing data to unauthorized spheres.