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 affects Statamic CMS, a Laravel and Git-powered CMS. The vulnerability is due to unsafe reflection caused by externally controlled input used in selecting classes or code during in-memory collection sorting. The prior fix for CVE-2026-41175 addressed this issue only in the query builder, leaving the in-memory sorting vulnerable. An attacker could manipulate sort parameters if a front-end template passes request input directly into a tag's sort parameter, potentially causing loss of content and assets. This vulnerability is not exploitable by default and requires explicit template configuration. The vulnerability is resolved in Statamic versions 5.73.23 and 6.20.0.
Potential Impact
The vulnerability can lead to loss of content and assets in affected Statamic CMS installations if exploited. There is no confidentiality impact reported. The attack complexity is high due to the need for specific template configuration, and no privileges or user interaction are required. There are no known exploits in the wild.
Mitigation Recommendations
This vulnerability has been fixed in Statamic CMS versions 5.73.23 and 6.20.0. Users should upgrade to these versions or later to remediate the issue. Since this is not exploitable by default, ensure that front-end templates do not pass visitor-controlled input into sort parameters if upgrading is not immediately possible.
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 affects Statamic CMS, a Laravel and Git-powered CMS. The vulnerability is due to unsafe reflection caused by externally controlled input used in selecting classes or code during in-memory collection sorting. The prior fix for CVE-2026-41175 addressed this issue only in the query builder, leaving the in-memory sorting vulnerable. An attacker could manipulate sort parameters if a front-end template passes request input directly into a tag's sort parameter, potentially causing loss of content and assets. This vulnerability is not exploitable by default and requires explicit template configuration. The vulnerability is resolved in Statamic versions 5.73.23 and 6.20.0.
Potential Impact
The vulnerability can lead to loss of content and assets in affected Statamic CMS installations if exploited. There is no confidentiality impact reported. The attack complexity is high due to the need for specific template configuration, and no privileges or user interaction are required. There are no known exploits in the wild.
Mitigation Recommendations
This vulnerability has been fixed in Statamic CMS versions 5.73.23 and 6.20.0. Users should upgrade to these versions or later to remediate the issue. Since this is not exploitable by default, ensure that front-end templates do not pass visitor-controlled input into sort parameters if upgrading is not immediately possible.
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/19/2026, 18:50:46 UTC
Last updated: 06/20/2026, 23:27:28 UTC
Views: 12
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.