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

New CVE Detected

CVE-2026-77140 – Unauthenticated Record Tampering (Broken Access Control) – TYPO3 “Telephone Directo

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

Summary

CVE-2026-77140 is a broken access control vulnerability in the TYPO3 "Telephone Directory" extension (Composer package jweiland/telephonedirectory) that allows an unauthenticated attacker to overwrite employee directory records. The extension validates an HMAC token on the frontend edit link only when the edit form is rendered, but not when the update is actually persisted, allowing the authorization check to be bypassed entirely. The issue carries a CVSS v4.0 base score of 8.7 (High), driven by network exploitability, no privileges/user interaction required, and high impact on data integrity.

Technical details

  • Root cause: The extension performs HMAC signature validation on the frontend "edit employee" link only in the controller action that renders the edit form. The action that actually persists (saves) the submitted change does not re-validate the HMAC, so the integrity/authorization check can be skipped entirely.
  • Trigger condition: An attacker only needs to know (or guess/enumerate) the UID of a visible employee record in the public-facing telephone directory.
  • Attack vector: The attacker crafts and sends a direct HTTP POST request to the update action of the extension, bypassing the normal flow of requesting a signed edit link first.
  • Impact: Unauthenticated modification (overwrite) of employee directory records — a violation of data integrity. No authentication, prior privileges, or user interaction are required to exploit the flaw.
  • Weakness classification: CWE-862 (Missing Authorization) and CWE-639 (Authorization Bypass Through User-Controlled Key).

Affected software

  • TYPO3 Extension "Telephone Directory" (jweiland/telephonedirectory), all versions 6.1.2 and below.

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade the "Telephone Directory" extension to version 6.2.0 or later via the TYPO3 extension manager, Packagist, or the official repository, where the update action now correctly re-validates the HMAC signature before persisting changes.
  • If immediate patching is not possible:
    • Restrict or disable public-facing frontend edit functionality for the telephone directory plugin until the update can be applied.
    • Use a web application firewall or reverse proxy rule to block direct POST requests to the extension’s update/edit endpoints from unauthenticated sources.
    • Monitor telephone directory records for unexpected/unauthorized modifications as a compensating detective control.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge