Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify TYPO3 site with Solr Enterprise Search extension
-
DeliveryHarvest valid Solr document IDs via legitimate search results or URL observation
-
ExploitCraft direct request to frontend detail-view endpoint with target document ID
-
ExecutionBypass siteHash filter and frontend user access filter
-
ImpactRetrieve access-controlled Solr document content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires that the target TYPO3 installation has the Apache Solr for TYPO3 Enterprise Search extension installed and the frontend detail-view feature enabled, which is a standard extension feature rather than a non-default configuration. The attacker must supply a valid Solr document ID, obtained by harvesting IDs from public search responses, from URL structures, or through enumeration if IDs follow predictable patterns - this is the primary limiting factor (reflected as AC:H and AT:P in the CVSS 4.0 vector). The CVSS 4.0 vector confirms PR:N, meaning no TYPO3 backend or frontend authentication is required to reach the vulnerable endpoint. Exploitation impact is bounded to confidentiality (VC:L); no write or denial-of-service capability is introduced. Sites where all Solr-indexed content is already publicly accessible are not materially affected, since the bypassed filters would not have blocked access to that content anyway. |
| Impact | The CVSS 4.0 vector (AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N, score 6.3) characterizes this as a network-reachable, unauthenticated bypass with limited confidentiality impact. AC:H and AT:P together indicate meaningful exploitation prerequisites: the attacker must obtain or guess a valid Solr document ID. These IDs may be harvested from search result responses, leaked via page URLs or referrer headers, or guessed through enumeration if they follow predictable patterns. No EPSS score was provided in the input data, so probabilistic exploitation likelihood cannot be independently quantified. The vulnerability is not listed in CISA KEV, and no POC is known, indicating no confirmed widespread exploitation. Real-world priority should be elevated for TYPO3 deployments where Solr indexes contain access-controlled content (e.g., members-only documents, multi-tenant content segregated by siteHash); sites where all indexed content is public face negligible additional exposure from this bypass. |
| Exploit ScenarioDerived | An attacker visits a public-facing TYPO3 site running the Solr Enterprise Search extension and performs several legitimate searches, harvesting Solr document IDs from the search result responses or from URLs exposed in the page. The attacker then issues direct requests to the frontend detail-view endpoint using those harvested IDs, bypassing the siteHash filter - allowing cross-site document access in multi-site deployments - and bypassing the frontend user access filter, retrieving documents that would normally require TYPO3 frontend authentication. No public POC is known at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
Frontend detail-view document lookup in the Apache Solr for TYPO3 Enterprise Search extension bypasses both the siteHash isolation filter and frontend user access controls, allowing retrieval of Solr-indexed documents outside normal authorization constraints. An unauthenticated visitor who obtains or guesses a valid Solr document ID can access content restricted to specific sites or authenticated frontend users by querying the detail-view endpoint directly, circumventing the access controls enforced on the regular search path. No public exploit code or CISA KEV listing exists at time of analysis; the CVSS 4.0 score of 6.3 with AC:H and AT:P reflects that exploitation depends on obtaining valid document IDs.
RemediationAI
The primary remediation is to upgrade the Apache Solr for TYPO3 Enterprise Search extension to the patched version specified in the TYPO3 security advisory at https://typo3.org/security/advisory/typo3-ext-sa-2026-025. The exact fixed version number is not confirmed in the available input data and must be retrieved directly from that advisory. As a compensating control pending patching, administrators can restrict access to the frontend detail-view endpoint at the web server or reverse proxy layer, for example by blocking or rate-limiting requests to the relevant TYPO3 plugin action URL, with the trade-off that legitimate detail-view functionality will be unavailable to end users. If the detail-view feature is not actively used by any site functionality, temporarily disabling it in extension configuration eliminates the vulnerable code path with no impact on the regular search experience.
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 affected product is the 'Apache Solr for TYPO3 - Enterprise Search' extension (CPE: cpe:2.3:a:typo3:extension_apache_solr_for_typo3_-_enterprise_search:*). TYPO3 is a PHP-based enterprise CMS, and this extension integrates Apache Solr full-text search. The siteHash is an extension-level mechanism that namespaces Solr indexes per site to prevent cross-site data bleed in multi-site TYPO3 installations. Frontend user access filters further restrict which indexed documents a given session can retrieve based on TYPO3 frontend authentication. The detail-view lookup route - a separate code path from the main search - omits both of these filter layers. The root cause class is CWE-639 (Authorization Bypass Through User-Controlled Key): the attacker supplies a Solr document ID as a user-controlled parameter and the application returns the document without verifying whether the caller is authorized to access it, because the authorization logic that exists elsewhere was simply not applied to this endpoint.
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:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Unauthenticated network access but requires obtaining a valid document ID (AC:H); impact is limited to partial confidentiality disclosure with no integrity or availability effect.
Primary rating from Vendor (TYPO3).
CVSS VectorVendor: TYPO3
Lifecycle Timeline
2DescriptionCVE.org
The extension's frontend detail-view document lookup does not apply the current site's siteHash filter or frontend user access filter, unlike the regular search path. A visitor who can obtain or guess a valid Solr document id can retrieve documents through this lookup without the same access restrictions enforced elsewhere.
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-65352
GHSA-9jvx-vcjh-9488
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB