Quick answers
- Is CVE-2026-54244 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54244 being exploited in the wild.
- How severe is CVE-2026-54244?
- Low severity, with a CVSS score of 3.5, published 17 July 2026.
- Which products and versions are affected?
- statamic/cms (Packagist) ECOSYSTEM:introduced=0,fixed=5.74.0; Statamic < 5.74.0, >= 6.0.0 < 6.20.3, < 5.74.0, >= 6.0.0, < 6.20.3.
- Is there a fix for CVE-2026-54244?
- Yes. statamic/cms (Packagist): upgrade to 5.74.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54244 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-54244?
- 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.74.0 or later
composer require statamic/cms:^5.74.0
Technical details
An incorrect authorization vulnerability (CWE-863) exists in Statamic CMS within the Live Preview functionality. The PreviewController.php component for existing entries and terms validated 'view' permissions but failed to enforce 'edit' permissions when processing caller-supplied field values. An authenticated Control Panel user with read-only access could submit arbitrary content to the preview endpoint and generate a shareable URL rendering that content. The attack requires network access and low privileges, with some user interaction required to view the generated preview. The issue is resolved in versions 5.74.0 and 6.20.3 by ensuring the endpoint requires proper edit authorization.
Affected products
- Statamic cms < 5.74.0, >= 6.0.0 < 6.20.3
Identifiers
- CVE-2026-54244
- GHSA-7mqq-4v55-88gh
Timeline
- 2026-06-08: patched: Fixes merged and released in v5.74.0 and v6.20.3
- 2026-06-09: advisory: GitHub Security Advisory published
- 2026-07-17: disclosed: CVE published to NVD