Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NSummary
CVE-2025-47226 is a medium-severity Forced Browsing (CWE-425) vulnerability in Snipeitapp Snipe-It. Its CVSS base score is 5.0 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 33% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
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
- 🇪🇺 ENISA EUVD: EUVD-2025-13304
Vulnerability Data
Grokability Snipe-IT before 8.1.0 has incorrect authorization for accessing asset information.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
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.
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.
Security testing can detect forced-browsing flaws, but the control itself does not prevent them in production.
Information access restriction implements the technical enforcement that directly blocks unauthorized direct requests.
Access control policy directly requires authorization checks on all resources, preventing forced browsing.
Managing access rights ensures every URL/script/file is explicitly authorized, mitigating direct request attacks.
Privileged access rights control enforces least-privilege checks on restricted endpoints.
Secure SDLC can include authorization design, yet the control itself does not guarantee runtime enforcement.