Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege frontend user
-
DeliveryAccess profile edit page rendered by femanager
-
ExploitSubmit modified form with target group identifier
-
ExecutionExtension skips authorization check on group field
-
PersistTYPO3 persists elevated group membership
-
ImpactAccess privileged frontend content or features
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: (1) the target TYPO3 site must have the femanager extension installed with the profile edit plugin active; (2) the profile edit plugin must be using its default field configuration - installations where the usergroup assignment field has been explicitly disabled or restricted in the plugin settings are NOT vulnerable; (3) the attacker must hold a valid authenticated frontend user session (PR:L - unauthenticated exploitation is not possible). Exploitation is limited to frontend user group escalation and does not directly affect backend administrator accounts. The AT:P requirement in the CVSS 4.0 vector confirms the default-configuration prerequisite as a concrete limiting factor. |
| Impact | The CVSS 4.0 score of 6.0 with vector AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N reflects a meaningful but gated risk: network reachable, low complexity, but requiring both an authenticated session (PR:L) and a specific deployment condition (AT:P - default field configuration). The high vulnerable-system confidentiality impact (VC:H) reflects that gaining membership in a privileged frontend group could expose protected content, members-only resources, or administrative frontend functions. No EPSS data was provided, limiting probabilistic exploitation assessment. KEV status is absent and no public POC is referenced, indicating no confirmed active exploitation at time of analysis. The practical risk is concentrated on TYPO3 sites using femanager for community or subscription features where frontend group membership gates access to sensitive material. Sites that have customized the profile edit plugin's field configuration to restrict or remove the groups field are not affected. The AT:P prerequisite is significant: default configuration is common among deployments that have not explicitly hardened femanager, so the effective vulnerable population is non-trivial. CVSS signals and description are consistent - no contradictions identified. |
| Exploit ScenarioDerived | An attacker with a valid low-privilege frontend user account on a TYPO3 site (e.g., a free-tier member or registered community user) navigates to the self-service profile edit page rendered by femanager. By manipulating the group assignment field in the submitted form - either through browser developer tools or a crafted HTTP request - the attacker includes the identifier of a privileged frontend group (such as a paid-subscription or administrator group). Because the extension lacks server-side authorization validation on this field in its default configuration, TYPO3 persists the new group membership. The attacker now has access to all content and features gated behind that privileged group. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
Self-service privilege escalation in the TYPO3 femanager (Frontend User Manager) extension allows any authenticated frontend user to assign themselves to arbitrary frontend usergroups via the profile edit plugin when operating under its default field configuration. The root cause is CWE-862 (Missing Authorization): the extension does not validate whether the requesting user is permitted to join the target group before processing the self-update. No public exploit has been identified at time of analysis, but the exploit path is straightforward for any logged-in frontend user on an affected TYPO3 installation. The CVSS 4.0 score of 6.0 reflects the prerequisite of an authenticated session and a specific configuration context.
RemediationAI
The primary remediation is to apply the patched version of the femanager extension as detailed in the TYPO3 security advisory at https://typo3.org/security/advisory/typo3-ext-sa-2026-024; an exact fix version was not confirmed from available intelligence data and must be retrieved from the advisory directly. As a compensating control pending patch deployment, administrators should immediately review the profile edit plugin's field configuration and explicitly remove or restrict the usergroup assignment field from the self-edit form - this directly eliminates the attack vector without requiring a code update, though it may impact legitimate self-service group management workflows. Alternatively, restricting access to the profile edit plugin to trusted user sessions or placing the profile edit page behind additional authentication checks reduces exposure. Administrators should audit existing frontend user accounts for unauthorized group memberships as part of incident assessment.
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
TYPO3 is a PHP-based enterprise content management system; femanager is a widely-used TYPO3 extension (CPE: cpe:2.3:a:typo3:extension_femanager) providing self-service frontend user registration and profile management. The profile edit plugin exposes a form through which authenticated frontend users may update their own account data. In its default field configuration, the group-assignment field is rendered without server-side authorization checks verifying whether the authenticated user has permission to join a given frontend usergroup. CWE-862 (Missing Authorization) precisely characterizes the root cause: the authorization gate exists in the access control model conceptually but is absent in the actual code path that processes the group field on self-update. The CVSS 4.0 vector includes AT:P (Attack Requirements: Present), confirming that exploitation depends on a specific prerequisite - the profile edit plugin must be deployed with default field configuration rather than a hardened custom one.
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:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Network reachable via profile edit form, authenticated session required (PR:L), no user interaction; high confidentiality from group escalation, low integrity from self-modification only.
Primary rating from Vendor (TYPO3).
CVSS VectorVendor: TYPO3
Lifecycle Timeline
1DescriptionCVE.org
The extension fails to restrict which frontend usergroups a logged-in user may assign to their own account when the profile edit plugin uses its default field configuration, allowing self-service privilege escalation into arbitrary frontend groups.
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.
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
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-65343
GHSA-qjph-66v6-w5fp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB