CVE-2026-49287: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') in statamic cms
Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.73.23 and 6.20.0, the fix for CVE-2026-41175 was incomplete. It addressed the issue in the query builder, but the same protection was not applied to in-memory collection sorting. Manipulating sort parameters could result in the loss of content and assets. This requires a front-end template that passes request input into a tag's sort parameter. It is not exploitable by default — a template would need to be explicitly set up to sort by a visitor-controlled value. This has been fixed in 5.73.23 and 6.20.0.
AI Analysis
Technical Summary
CVE-2026-49287 is a vulnerability in Statamic CMS involving unsafe reflection due to externally-controlled input used in selecting classes or code during in-memory collection sorting. The prior fix for CVE-2026-41175 addressed the query builder but did not cover sorting, allowing manipulation of sort parameters to cause content and asset loss. Exploitation requires a front-end template that passes user input into sorting parameters, which is not the default configuration. The issue is resolved in Statamic CMS versions 5.73.23 and 6.20.0.
Potential Impact
The vulnerability can result in loss of content and assets if exploited. However, exploitation is not straightforward as it requires a specific template setup that passes visitor-controlled input into sorting parameters. There is no indication of confidentiality or availability impact beyond content and asset loss. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade Statamic CMS to version 5.73.23 or later, or 6.20.0 or later, where this vulnerability has been fixed. Since the vulnerability requires explicit template configuration to be exploitable, review and avoid passing untrusted user input into sorting parameters in templates as a preventive measure.
CVE-2026-49287: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') in statamic cms
Description
Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.73.23 and 6.20.0, the fix for CVE-2026-41175 was incomplete. It addressed the issue in the query builder, but the same protection was not applied to in-memory collection sorting. Manipulating sort parameters could result in the loss of content and assets. This requires a front-end template that passes request input into a tag's sort parameter. It is not exploitable by default — a template would need to be explicitly set up to sort by a visitor-controlled value. This has been fixed in 5.73.23 and 6.20.0.
CVSS v3.1
Score 7.4high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-49287 is a vulnerability in Statamic CMS involving unsafe reflection due to externally-controlled input used in selecting classes or code during in-memory collection sorting. The prior fix for CVE-2026-41175 addressed the query builder but did not cover sorting, allowing manipulation of sort parameters to cause content and asset loss. Exploitation requires a front-end template that passes user input into sorting parameters, which is not the default configuration. The issue is resolved in Statamic CMS versions 5.73.23 and 6.20.0.
Potential Impact
The vulnerability can result in loss of content and assets if exploited. However, exploitation is not straightforward as it requires a specific template setup that passes visitor-controlled input into sorting parameters. There is no indication of confidentiality or availability impact beyond content and asset loss. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade Statamic CMS to version 5.73.23 or later, or 6.20.0 or later, where this vulnerability has been fixed. Since the vulnerability requires explicit template configuration to be exploitable, review and avoid passing untrusted user input into sorting parameters in templates as a preventive measure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-28T20:07:58.862Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a358c5cf198dc38c1f2fbcc
Added to database: 06/19/2026, 18:37:16 UTC
Last enriched: 06/26/2026, 19:22:13 UTC
Last updated: 08/04/2026, 19:11:01 UTC
Views: 78
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.