Security Resilience

CVE-2025-48202

Published
21 May 2025
Modified
17 June 2026
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0030 21th percentile
Risk Priority 43 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-48202 is a medium-severity Forced Browsing (CWE-425) vulnerability in Typo3 (inferred from references). Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The femanager extension through 8.2.1 for TYPO3 allows Insecure Direct Object Reference.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1491.002 External Defacement Impact
An adversary may deface systems external to an organization in an attempt to deliver messaging, intimidate, or otherwise mislead an organization or users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-41404Shared CWE-425
CVE-2023-28160Shared CWE-425
CVE-2025-57823Shared CWE-425
CVE-2025-6352Shared CWE-425
CVE-2025-67844Shared CWE-425
CVE-2023-44320Shared CWE-425
CVE-2026-0790Shared CWE-425
CVE-2024-39868Shared CWE-425
CVE-2023-5702Shared CWE-425
CVE-2026-36453Shared CWE-425

Affected Assets

Typo3
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

AC-3 directly requires enforcement of authorizations for access to resources such as URLs, scripts, and files, structurally preventing forced browsing.

AC-24 requires that access-control decisions be applied to every request, addressing the missing enforcement on restricted URLs.

AC-6 requires restricting authorizations to the minimum needed, reducing the set of resources that must be protected against direct requests.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
blocks

Directly requires policy-driven definition, enforcement, and review of authorizations on resources such as URLs.

PR.IR-01 mostly match
blocks

Protects environments from unauthorized logical access, which includes preventing direct requests to restricted paths.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.15 directly requires defining/implementing access control rules, authorization, need-to-know, and restrictions that enforce appropriate access on all URLs/resources, which stops forced browsing exploitation even if the flaw remains; remainder is bounded to non-authorization cases like path traversal or CSRF (per AC-3 anchor).

finds

Security testing can detect forced-browsing flaws, but the control itself does not prevent them in production.

blocks

Information access restriction implements the technical enforcement that directly blocks unauthorized direct requests.

prevents

Secure coding practices reduce the likelihood of missing authorization checks, yet do not guarantee coverage.

References