Broken Access Control in extension "femanager"

published 2023-12-13 2 y ago modified 2026-09-22 47 d ago also GHSA-4xp5-hr35-84cx , EUVD-2023-60685

cvss: 5.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits: 0; none known

An issue was discovered in the femanager extension 7.x before 7.2.3 for TYPO3. It fails to check access permissions for the edit user component. An authenticated frontend user can exploit this to either edit data of various frontend users or delete various frontend user accounts.

Patch / fix

fixed in 2

packagist in2code/femanager 7.2.3
TYPO3 femanager 7.2.3

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 55 d ago (2026-09-14)

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
GitHub	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	in2code/femanager	>=7.0.0, <7.2.3	7.2.3

Affected products

TYPO3 femanager

Classification

Weakness

CWE-863 Incorrect Authorization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary