Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege TYPO3 account
-
DeliveryTrigger Apache Solr indexer sub-request
-
ExploitExtension writes forged empty access restrictions into shared rootline cache
-
ExecutionAnonymous visitor requests extendToSubpages-protected page
-
PersistPoisoned cache serves page without access controls applied
-
ImpactRestricted content disclosed to unauthorized visitor
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires low-privilege authenticated access to initiate Apache Solr indexer sub-requests on the target TYPO3 instance, confirmed by PR:L in the CVSS 4.0 vector. The target site must be actively using TYPO3's extendToSubpages feature for frontend-group-based page access control - protected pages must rely on inherited restrictions for the bypass to expose restricted content. The AT:P attack requirement indicates an additional specific prerequisite condition must be met, such as a particular cache population state or indexer execution timing. What limits exploitation: low-privilege authenticated access is required to trigger the indexer (not unauthenticated); high attack complexity (AC:H) indicates conditions are not trivially reproducible; the specific prerequisite condition (AT:P) adds another barrier; and sites that do not use extendToSubpages-based frontend access controls are not exposed to the described confidentiality or integrity impact. |
| Impact | The CVSS 4.0 vector (AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H) confirms that exploitation is network-reachable but non-trivial: low-privilege authenticated access is required to initiate the indexer sub-request, a specific prerequisite condition (AT:P) must be present, and high attack complexity (AC:H) indicates exploitation is not straightforwardly automatable or scriptable at scale. However, the cache-poisoning mechanism gives this vulnerability a disproportionate blast radius per exploitation event - a single successful trigger can expose protected content to every anonymous visitor until the cache is explicitly flushed or expires. EPSS data was not included in the provided intelligence, leaving probabilistic exploitation likelihood unquantified; this is a notable gap for defenders performing quantitative triage. This CVE is not listed in CISA KEV, and no public exploit code has been identified. The combination of missing EPSS, no KEV listing, and high attack complexity suggests this is not currently subject to mass or automated exploitation, but the severity of the cache-poisoning impact means that any TYPO3 operator relying on extendToSubpages-based access controls should treat patching as a priority rather than deferring. |
| Exploit ScenarioDerived | An attacker with low-privilege authenticated access to a TYPO3 instance triggers an Apache Solr indexer sub-request; the extension writes forged empty frontend-group and subpage-inheritance values into the shared TYPO3 rootline cache. Any anonymous visitor who subsequently requests a page protected by inherited extendToSubpages restrictions receives the cached, restriction-free response and can read content they are not authorized to access. No public proof-of-concept has been identified, and the high attack complexity and specific prerequisite condition suggest this is not a push-button exploit. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
Cache-poisoning-based access control bypass in the Apache Solr for TYPO3 Enterprise Search extension allows anonymous visitors to read pages that should be protected by extendToSubpages-inherited frontend-group restrictions. The extension fails to isolate its forged access-restriction state during indexer sub-requests, writing empty frontend-group and subpage-inheritance flags into the shared TYPO3 rootline cache, where they persist and serve subsequent user requests without the original restrictions applied. No public exploit code has been identified at time of analysis, but the CVSS 4.0 score of 7.6 with combined high confidentiality and integrity impact reflects meaningful severity for any TYPO3 deployment relying on page-level inherited access controls.
RemediationAI
Apply the patched extension release identified in the TYPO3 security advisory at https://typo3.org/security/advisory/typo3-ext-sa-2026-025; exact fixed version numbers are not confirmed in the available intelligence and must be sourced from that advisory. As an interim compensating control, disabling or restricting access to the Solr indexer trigger endpoint reduces exposure, though this will suspend search index updates and degrade search result freshness. Additionally, scheduling periodic flushes of the TYPO3 rootline page cache after each indexer run can limit the persistence window of a poisoned cache state; note that this does not prevent re-poisoning on subsequent indexer executions and adds operational overhead. Sites that do not use extendToSubpages-inherited frontend-group access controls are not meaningfully exposed to the confidentiality or integrity impacts of this vulnerability.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerable product is the Apache Solr for TYPO3 Enterprise Search extension (CPE: cpe:2.3:a:typo3:extension_"apache_solr_for_typo3_-_enterprise_search":*). TYPO3 CMS uses a shared rootline cache to store page-level access control metadata, including frontend user group assignments and the extendToSubpages flag, which propagates access restrictions to descendant pages. During Solr indexer sub-requests, the extension simulates an unprivileged browsing context by forging empty values for frontend-group and subpage-inheritance restrictions on page records. Critically, this forged state is written into the shared rootline cache rather than being isolated to the indexer request scope, causing the cache to reflect bypassed access controls for all subsequent requests by any visitor. CWE-862 (Missing Authorization) is the precise root cause: the extension performs a cache-write operation without enforcing or restoring the correct authorization context, allowing forged low-privilege data to contaminate the shared cache and persist across unrelated user sessions.
Know when Typo3 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Low-privilege access needed to trigger indexer (PR:L); cache poisoning affects other users' sessions so scope changes (S:C); no availability impact observed.
Primary rating from Vendor (TYPO3).
CVSS VectorVendor: TYPO3
Lifecycle Timeline
2DescriptionCVE.org
The extension forces empty frontend-group and subpage-inheritance restrictions onto page records during indexer sub-requests, and this forged state was persisted into the shared rootline cache, allowing anonymous visitors to bypass extendToSubpages-inherited access restrictions on cached pages.
Executive ViewAI
Apache Solr for TYPO3 Enterprise Search extension contains a cache-poisoning vulnerability that bypasses page-level access controls, allowing unauthorized access to confidential content intended for specific user groups. Organizations running this extension face immediate risk of exposing sensitive employee data, customer information, and internal documents to unauthorized visitors due to persistent cache contamination across user sessions.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) disable Solr query result caching; (2) restrict Solr indexer service account permissions to non-sensitive content and read-only operations; (3) implement cache layer separation to prevent indexer requests from contaminating user-facing caches; (4) force complete cache invalidation whenever access control rules change; (5) deploy active monitoring on Solr query logs and TYPO3 access events for indicators of exploitation.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
In TYPO3 installations with the "mediace" extension from version 7.6.2 and before version 7.6.5, it has been discovered
Server-side template injection in the TYPO3 'Powermail' extension lets an anonymous user submit Fluid template syntax th
Unrestricted File Upload vulnerability in the fileDenyPattern in sysext/core/Classes/Core/SystemEnvironmentBuilder.php i
Remote code execution in the TYPO3 'Content Element Selector' extension allows unauthenticated attackers to execute arbi
The frontend rendering component in TYPO3 4.5.x before 4.5.39, 4.6.x through 6.2.x before 6.2.9, and 7.x before 7.0.2, w
Broken referrer enforcement in TYPO3 CMS backend and Install Tool allows an attacker with JavaScript execution capabilit
Cross-site scripting (XSS) vulnerability in the Backend component in TYPO3 6.2.x before 6.2.19 allows remote attackers t
TYPO3 is a free and open source Content Management Framework released under the GNU General Public License. Rated medium
TYPO3 is an open source PHP based web content management system. Rated medium severity (CVSS 6.1), this vulnerability is
TYPO3 Fluid before versions 2.0.8, 2.1.7, 2.2.4, 2.3.7, 2.4.4, 2.5.11 and 2.6.10 is vulnerable to Cross-Site Scripting.
TYPO3 Fluid Engine (package `typo3fluid/fluid`) before versions 2.0.5, 2.1.4, 2.2.1, 2.3.5, 2.4.1, 2.5.5 or 2.6.1 is vul
svg.swf in TYPO3 6.2.0 to 6.2.38 ELTS and 7.0.0 to 7.1.0 could allow an unauthenticated, remote attacker to conduct a cr
EUVD-2026-65353
GHSA-2cv3-mmc6-j68f
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB