Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify public TYPO3 page with femanager Detail/List plugin
-
ExploitManipulate uid parameter in HTTP request
-
ExecutionRetrieve arbitrary frontend user profile record
-
ImpactEnumerate additional IDs to harvest full user database
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 femanager extension is installed on the TYPO3 instance and that at least one page containing the femanager Detail or List plugin is publicly accessible without frontend authentication. The AT:P prerequisite in the CVSS 4.0 vector reflects this plugin-availability dependency. What limits exploitation: if femanager Detail and List plugin pages are placed behind a TYPO3 frontend login wall (requiring authenticated frontend users), the IDOR remains exploitable by any authenticated frontend user performing horizontal privilege escalation against other users' records - it is not fully mitigated by requiring login. Exploitation is constrained to confidentiality impact only; no write access to user records or system-level impact is implied. TYPO3 installations that do not use the femanager extension, or that have not deployed Detail or List plugins on any page, are not affected. |
| Impact | The CVSS 4.0 base score of 8.2 (High) reflects a network-accessible, unauthenticated confidentiality breach with no integrity or availability impact. The AT:P (Attack Requirements: Present) metric is the critical moderating factor: exploitation is conditional on the femanager Detail or List plugin being deployed and publicly reachable, which is precisely its intended use-case deployment, making the prerequisite low-friction in practice. VC:H confirms that full frontend user profile records - including PII such as email, date of birth, and address - are exposed. There is no EPSS data available in the source intelligence, and the vulnerability is not listed in CISA KEV, suggesting no confirmed mass exploitation. The absence of Integrity and Availability impact (VI:N, VA:N, SC:N, SI:N, SA:N) limits the attack surface to data exfiltration. Real-world risk is meaningful for any TYPO3 installation using femanager for customer or member self-service portals where user PII is stored; the GDPR and data-protection exposure for affected organisations elevates operational impact beyond the technical CVSS score alone. |
| Exploit ScenarioDerived | An unauthenticated attacker visits a publicly accessible TYPO3 page that renders the femanager Detail plugin and appends or modifies the uid parameter in the request (e.g., ?tx_femanager_pi1[user]=42) to enumerate integer user IDs sequentially, harvesting full profile records - name, email, date of birth, and address - for every registered frontend user without any credentials. No public exploit code has been identified at time of analysis, but the technique requires no specialised tooling beyond a basic HTTP client or browser. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
Insecure Direct Object Reference in the TYPO3 femanager extension exposes frontend user profile data - including name, email address, date of birth, and postal address - to any unauthenticated visitor who can reach the Detail or List plugin. The extension's user detail view accepts a caller-supplied user ID without validating that the requested record belongs to the configured or authenticated target, making horizontal privilege escalation trivial via ID enumeration. No active exploitation has been confirmed (not listed in CISA KEV), and no public exploit code has been identified at time of analysis.
RemediationAI
The primary fix is to update the femanager extension to the patched release identified in the vendor advisory at https://typo3.org/security/advisory/typo3-ext-sa-2026-024; a specific patched version number is not confirmed in the available intelligence and should be taken directly from that advisory. As an immediate compensating control prior to patching, restrict public access to any TYPO3 pages containing femanager Detail or List plugins through TYPO3 page-access restrictions, requiring frontend login before the plugin is rendered - this limits the exploitable surface to authenticated users and trades off self-service usability for unauthenticated visitors. Alternatively, temporarily remove or disable femanager Detail plugin instances from public page layouts in the TYPO3 backend until the patch is applied. Backend-level IP restriction of the affected pages is a further option where all legitimate users originate from known network ranges.
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
femanager is a TYPO3 CMS extension providing frontend user self-management capabilities, including profile viewing and editing via the Detail and List content plugins. The CPE string cpe:2.3:a:typo3:extension_"femanager":*:*:*:*:*:*:*:* with a wildcard version range indicates all released versions are affected. The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key): the controller action that renders a user's detail view accepts a uid parameter from the HTTP request and performs a database lookup without asserting that the retrieved record matches the session-authenticated user or the record configured by the TYPO3 backend editor. This is a classic IDOR pattern - the object reference (uid) is trusted as an access control mechanism rather than verified against an authorisation policy.
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:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable plugin, no authentication or user interaction needed, confidentiality-only impact on vulnerable system with unchanged scope.
Primary rating from Vendor (TYPO3).
CVSS VectorVendor: TYPO3
Lifecycle Timeline
2DescriptionCVE.org
The extension's user detail view fails to verify that a requested user record matches the configured or logged-in target, allowing any visitor with access to the Detail or List plugin to retrieve another frontend user's profile data, including name, email, date of birth and address, by supplying an arbitrary user ID.
Executive ViewAI
TYPO3 femanager extension contains an insecure direct object reference (IDOR) that exposes customer personally identifiable information-names, email addresses, dates of birth, and postal addresses-to unauthenticated users; no public exploit identified at time of analysis. Organizations running this extension face immediate data breach risk and compliance violation exposure without an available vendor patch. Remediation requires urgent inventory, access restrictions, and compensating controls to prevent customer PII disclosure.
No vendor-released patch identified at time of analysis. Implement Web Application Firewall rules to detect and block user ID enumeration attempts; apply aggressive rate limiting to user detail and list endpoints; enable detailed logging and alerting on sequential ID access patterns; disable femanager extension entirely if operationally feasible; restrict affected plugins to authenticated users only via conditional access controls; monitor third-party TYPO3 security forums and vendor advisories for patch availability.
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-65341
GHSA-279q-wx34-jv34
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB