Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-33887: Statamic is a Laravel and Git powered content management system (CMS)

20
Routine
MEDIUM 5.4UPGRADE

CVE-2026-33887 is a medium-severity flaw (CVSS 5.4) affecting statamic. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.16 and 6.7.2, 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 wi

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score5.4 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.1% (top 96%)
CISA exploited listNo
WeaknessCWE-862
Published2026-03-27
Last modified2026-10-26
Publisher (CNA): GitHub, Inc. · Vendor: statamic

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

statamic statamic UPGRADE
Affected: < 5.73.16 · >= 6.0.0 and < 6.7.2
Fixed in: 5.73.16, 6.7.2
Safe to downgrade to: a release before 6.0.0
1. Check installed version
apt-cache policy statamic || rpm -q statamic || statamic --version
2. UPGRADE to 5.73.16 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade statamic
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade statamic
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 6.0.0 (Debian / Ubuntu)
apt-cache madison statamic sudo apt install statamic=<VERSION_BEFORE_6.0.0> sudo apt-mark hold statamic
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list statamic sudo dnf downgrade statamic-<VERSION_BEFORE_6.0.0> sudo dnf versionlock add statamic
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-33887?

statamic: upgrade to 5.73.16, 6.7.2. Exact commands for each OS are on this page.

Is CVE-2026-33887 being exploited?

CVE-2026-33887 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-33887 affect?

CVE-2026-33887 affects statamic. Severity is medium (CVSS 5.4). Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.16 and 6.7.2, authenticated Control Panel users could view entry revisions for any collection with revisions enabled, regardless of whether they h

How urgent is CVE-2026-33887?

Priority 20/100. No elevated risk signals yet.

Software pages

Laravel vulnerabilities · Git vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.