Skip to main content

TYPO3 femanager CVE-2026-77135

| EUVDEUVD-2026-65341 HIGH
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-08-25 TYPO3 GHSA-279q-wx34-jv34
8.2
CVSS 4.0 · Vendor: TYPO3
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify public TYPO3 page with femanager Detail/List plugin
  2. Exploit
    Manipulate uid parameter in HTTP request
  3. Execution
    Retrieve arbitrary frontend user profile record
  4. Impact
    Enumerate 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Extension "femanager" 0 <6.4.5
Extension "femanager" 8.0.0 <8.4.2
Extension "femanager" 7.0.0 <7.5.5
Extension "femanager" 13.0.0 <13.3.5

Affected Packages

euvd extension_femanager fix: 6.4.5, 7.5.5, 8.4.2, 13.3.5

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

Vendor (TYPO3) PRIMARY 8.2 HIGH
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
vuln.today AI 7.5 HIGH

Network-reachable plugin, no authentication or user interaction needed, confidentiality-only impact on vulnerable system with unchanged scope.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (TYPO3).

CVSS VectorVendor: TYPO3

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Aug 25, 2026 - 11:01 EUVD
CVE Published
Aug 25, 2026 - 09:00 cve.org
HIGH 8.2

DescriptionCVE.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

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.2%
Top 85% exploitable
Prevalence
Low
TYPO3 CMS has significant European enterprise use but limited global footprint
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +41
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in Typo3

View all
CVE-2020-15086 CRITICAL POC
9.8 Jul 29

In TYPO3 installations with the "mediace" extension from version 7.6.2 and before version 7.6.5, it has been discovered

CVE-2026-77136 CRITICAL POC
9.5 Aug 25

Server-side template injection in the TYPO3 'Powermail' extension lets an anonymous user submit Fluid template syntax th

CVE-2017-14251 HIGH POC
8.8 Sep 11

Unrestricted File Upload vulnerability in the fileDenyPattern in sysext/core/Classes/Core/SystemEnvironmentBuilder.php i

CVE-2026-46725 CRITICAL POC
9.2 May 19

Remote code execution in the TYPO3 'Content Element Selector' extension allows unauthenticated attackers to execute arbi

CVE-2014-9509 HIGH POC
7.5 Jan 04

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

CVE-2026-19418 HIGH POC
7.3 Aug 11

Broken referrer enforcement in TYPO3 CMS backend and Install Tool allows an attacker with JavaScript execution capabilit

CVE-2016-4056 MEDIUM POC
6.1 Jan 23

Cross-site scripting (XSS) vulnerability in the Backend component in TYPO3 6.2.x before 6.2.19 allows remote attackers t

CVE-2023-24814 MEDIUM POC
6.1 Feb 07

TYPO3 is a free and open source Content Management Framework released under the GNU General Public License. Rated medium

CVE-2020-26227 MEDIUM POC
6.1 Nov 23

TYPO3 is an open source PHP based web content management system. Rated medium severity (CVSS 6.1), this vulnerability is

CVE-2020-26216 MEDIUM POC
6.1 Nov 17

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.

CVE-2020-15241 MEDIUM POC
6.1 Oct 08

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

CVE-2020-8091 MEDIUM POC
6.1 Jan 27

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

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy