Quick answers
- Is CVE-2026-49287 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49287 being exploited in the wild.
- How severe is CVE-2026-49287?
- High severity, with a CVSS score of 7.4, published 19 June 2026.
- Which products and versions are affected?
- statamic/cms (Packagist) ECOSYSTEM:introduced=0,fixed=5.73.23; Statamic < 5.73.23, >= 6.0.0 < 6.20.0, < 5.73.23, >= 6.0.0, < 6.20.0.
- Is there a fix for CVE-2026-49287?
- Yes. statamic/cms (Packagist): upgrade to 5.73.23 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49287 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-49287?
- Check whether you run statamic/cms (Packagist) or Statamic at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- statamic/cms (Packagist): upgrade to 5.73.23 or later
composer require statamic/cms:^5.73.23
Technical details
Statamic CMS is vulnerable to unsafe reflection (CWE-470) due to an incomplete fix for a previous vulnerability. The issue resides in how the CMS handles in-memory collection sorting when sort parameters are passed directly from request input to a template tag. An attacker can manipulate these sort parameters to invoke unintended methods, potentially leading to the deletion of content and assets. This vulnerability is only exploitable if a front-end template is explicitly configured to use visitor-controlled values for sorting. Patches are available in versions 5.73.23 and 6.20.0.
Affected products
- Statamic Statamic CMS < 5.73.23, >= 6.0.0, < 6.20.0
Identifiers
- CVE-2026-49287
- GHSA-m92m-r54r-x8r2
Timeline
- 2026-05-25: disclosed
- 2026-06-19: advisory: NVD publication date
- 2026-06-26: advisory: GitHub Advisory published