MediumGHSA-4hp7-3wxg-cv9qCVE-2026-33887

Statamic allows unauthorized content access through missing authorization in its revision controllers

Published 26 Mar 2026 · Updated 27 Mar 2026

Affected packages

statamic/cmsComposer

Affected: <5.73.16
Fixed in: 5.73.16

Update to the fixed version for your release line, for example:composer require statamic/cms:^5.73.16

statamic/cmsComposer

Affected: >=6.0.0-alpha.1 <6.7.2
Fixed in: 6.7.2

Update to the fixed version for your release line, for example:composer require statamic/cms:^6.7.2

Details

Impact

Authenticated Control Panel users could view entry revisions for any collection with revisions enabled, regardless of whether they had the required collection permissions. This bypasses the authorization checks that the main entry controllers enforce, exposing entry field values and blueprint data.

Users could also create entry revisions without edit permission, though this only snapshots the existing content state and does not affect published content.

Patches

This has been fixed in 5.73.16 and 6.7.2.

Is GHSA-4hp7-3wxg-cv9q in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected statamic/cms, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.