CVE-2026-33884: Statamic's live preview token bypasses content protection for unrelated entries

CVE-2026-33884 · Severity: medium · CVSS 4.3 · Published 2026-03-27

Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.16 and 6.7.2, an authenticated Control Panel user with access to live preview could use a live preview token to access restricted content that the token was not intended for. This has been fixed in 5.73.16 and 6.7.2.

Technologies: statamic/cms (Packagist), Statamic. Vendors: Packagist, Statamic.

Quick answers

Is CVE-2026-33884 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-33884 being exploited in the wild.
How severe is CVE-2026-33884?
Medium severity, with a CVSS score of 4.3, published 27 March 2026.
Which products and versions are affected?
statamic/cms (Packagist) ECOSYSTEM:introduced=0,fixed=5.73.16.
Is there a fix for CVE-2026-33884?
Yes. statamic/cms (Packagist): upgrade to 5.73.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-33884?
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.16 or later
    composer require statamic/cms:^5.73.16

Affected products

  • statamic/cms (Packagist) ECOSYSTEM:introduced=0,fixed=5.73.16
  • Statamic

Identifiers

  • CVE-2026-33884
  • GHSA-8vwx-ccf6-5wg2

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.