CVE-2026-49287: Statamic CMS vulnerable to unsafe method invocation via collection sorting allows data destruction

Published Jun 19, 2026
·
Updated

Impact

The fix for GHSA-4jjr-vmv7-wh4w 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.

Patches

This has been fixed in 5.73.23 and 6.20.0.

Other sources

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.

MITRE

Affected Software

3 affected componentsFixes available
Statamic Statamic CMS<5.73.23, <6.20.0
composer/statamic/cms>=6.0.0<6.20.0
6.20.0
composer/statamic/cms<5.73.23
5.73.23

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/statamic/cms to a version that resolves this vulnerability.

    Fixed in 6.20.0
  2. Upgrade

    Upgrade composer/statamic/cms to a version that resolves this vulnerability.

    Fixed in 5.73.23
  3. Upgrade

    Upgrade Statamic CMS to a version that resolves this vulnerability.

    Fixed in 5.73.23Patch GHSA-4jjr-vmv7-wh4w
  4. Upgrade

    Upgrade Statamic CMS to a version that resolves this vulnerability.

    Fixed in 6.20.0Patch GHSA-4jjr-vmv7-wh4w

Event History

Jun 19, 2026
CVE Published
via MITRE·05:36 PM
Data Sourced
via MITRE·05:36 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeakness
Jun 26, 2026
Advisory Published
via GitHub·10:15 PM
Data Sourced
via GitHub·10:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-49287?

The severity of CVE-2026-49287 is high, with a score of 7.4.

2

How do I fix CVE-2026-49287?

To fix CVE-2026-49287, upgrade Statamic to version 5.73.23 or 6.20.0 or later.

3

What does CVE-2026-49287 affect?

CVE-2026-49287 affects the Statamic CMS and specifically involves unsafe method invocation during collection sorting.

4

What are the risks associated with CVE-2026-49287?

The risks associated with CVE-2026-49287 include potential data destruction due to unsafe manipulation of sort parameters.

5

Who is affected by CVE-2026-49287?

Any users running versions of Statamic CMS prior to 5.73.23 and 6.20.0 are affected by CVE-2026-49287.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203