Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-77134 – Account Approval Bypass / Privilege Escalation – TYPO3 femanager Extension (<6.4.5,

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-77134 is an incorrect authorization vulnerability (CWE-863) in the TYPO3 "femanager" frontend user management extension (in2code/femanager). The flaw allows an unauthenticated visitor to self-approve a pending user account that is configured to require administrator approval, effectively bypassing the intended admin gatekeeping step. The vulnerability carries a CVSS v4.0 base score of 8.3 (High) and was disclosed by TYPO3 as part of advisory TYPO3-EXT-SA-2026-024.

Technical details

  • Root cause: femanager’s admin-approval workflow does not validate that the confirmation token presented belongs to a dedicated admin-approval hash. It instead accepts the regular user self-confirmation hash for the same purpose.
  • Trigger condition: The regular confirmation hash can be freely obtained by any visitor through the extension’s public "resend confirmation" action, without prior authentication.
  • Attack vector: Network — an attacker registers or targets a pending account, retrieves the standard confirmation hash via the public resend-confirmation endpoint, then replays that hash against the admin-approval action to activate the account without administrator involvement.
  • Impact: Unauthorized activation of accounts that were meant to be gated behind manual administrator review, potentially granting the attacker legitimate frontend access and any privileges tied to approved accounts on the affected TYPO3 site.
  • This issue was disclosed alongside three other femanager vulnerabilities (privilege escalation via self-assigned usergroups, an information disclosure issue in the Detail/List plugin, and an account-takeover issue in the invitation controller), all fixed in the same release round.

Affected software

  • TYPO3 extension femanager (in2code/femanager):
    • Versions 0 – 6.4.4 (fixed in 6.4.5)
    • Versions 7.0.0 – 7.5.4 (fixed in 7.5.5)
    • Versions 8.0.0 – 8.4.1 (fixed in 8.4.2)
    • Versions 13.0.0 – 13.3.4 (fixed in 13.3.5)

Severity

  • CVSS v4.0 Base Score: 8.3 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade femanager to the patched release corresponding to your branch — 6.4.5, 7.5.5, 8.4.2, or 13.3.5 — via Composer or the TYPO3 Extension Manager.
  • If patching is not immediately possible:
    • Disable or restrict public access to the femanager "resend confirmation" action until the update can be applied.
    • Review any frontend user accounts activated recently that were originally configured to require admin approval, and manually verify their legitimacy.
    • Follow the TYPO3 Security Guide for additional hardening of extension-based frontend authentication workflows.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge