CVE-2026-41175
Statamic ≤ 5.73.20
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HSummary
CVE-2026-41175 is a high-severity Unsafe Reflection (CWE-470) vulnerability in Statamic Statamic. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Reflective Code Loading (T1620); ranked at the 23th 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 SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-41175 is a vulnerability in Statamic, a Laravel and Git-powered content management system (CMS), affecting versions prior to 5.73.20 and 6.13.0. It stems from CWE-470 (Use of Externally-Controlled Input to Select Classes or Code) and allows attackers to manipulate query parameters on Control Panel endpoints, REST API endpoints, or arguments in GraphQL queries. This manipulation can result in the deletion of content, assets, and user accounts. The issue has a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H), indicating high severity due to network accessibility, low attack complexity, and significant impacts on integrity and availability.
Attackers can exploit this vulnerability in different ways depending on the endpoint. For Control Panel endpoints, an authenticated user with minimal permissions—such as "view entries" to delete entries or "view users" to delete users—can perform destructive actions remotely. REST API and GraphQL exploits require no permissions or authentication but are not enabled by default; they demand explicit configuration without authentication and enabling specific resources. Successful exploitation leads to unauthorized deletion of site content, assets, and user accounts.
The Statamic security advisory at https://github.com/statamic/cms/security/advisories/GHSA-4jjr-vmv7-wh4w details the fix in versions 5.73.20 and 6.13.0. Sites enabling REST or GraphQL APIs without authentication should prioritize patching as critical, while others should update promptly to mitigate risks from low-privilege Control Panel users.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-25108
Vulnerability Data
Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.20 and 6.13.0, manipulating query parameters on Control Panel and REST API endpoints, or arguments in GraphQL queries, could result in the loss of content, assets,…
more
and user accounts. The Control Panel requires authentication with minimal permissions in order to exploit. e.g. "view entries" permission to delete entries, or "view users" permission to delete users, etc. The REST and GraphQL API exploits do not require any permissions, however neither are enabled by default. In order to be exploited, they would need to be explicitly enabled with no authentication configured, and the specific resources enabled too. Sites that enable the REST or GraphQL API without authentication should treat patching as critical priority. This has been fixed in 5.73.20 and 6.13.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly stops externally supplied class or method names from selecting improper code via reflection.
Enforces authorization checks on the code or classes ultimately invoked, blocking unauthorized selections even if reflection is used.
Limits privileges of any code reached through unsafe reflection, reducing blast radius without stopping the selection itself.
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.
Secure SDLC practices directly avoid introducing externally controlled class selection via reflection.
Vulnerability identification processes can discover unsafe reflection during code review or scanning.
Preventing execution of unauthorized code can block exploitation of unsafe reflection at runtime.
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.
Secure coding standards directly forbid unsafe reflection and require whitelisting or static alternatives.
Security testing can detect and block unsafe reflection patterns before release.
Secure development lifecycle mandates input validation and design reviews that reduce unsafe reflection risks.
Application security requirements can explicitly prohibit or constrain reflection based on untrusted input.
Secure architecture principles discourage dynamic class loading from external data sources.
Access restrictions limit who can supply the malicious input but do not address the reflection flaw itself.