dbcve.org
StatamicApplication

CVE-2026-33887

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 5.73.16 / 6.7.2 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 without edit permission, though this only snapshots the existing content state and does not affect published content. This has been fixed in 5.73.16 and 6.7.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Statamic CMS versions prior to 5.73.16 and 6.7.2 contain an IDOR/broken access control vulnerability where the revision controller bypasses collection permission checks. Authenticated Control Panel users can view entry revisions for any collection with revisions enabled and create revisions without edit permissions, exposing sensitive entry field values and blueprint data.

MitigationUpgrade Statamic to version 5.73.16 or 6.7.2 or later to apply the vendor patch that enforces proper authorization checks on revision controllers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StatamicApplication
Affected:< 5.73.16>= 6.0.0, < 6.7.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Statamic CMS installed version
    Check the version file in your Statamic installation (composer.json or a version file in the statamic core directory) or run 'php artisan statamic:version' if available
    Affected if The installed version is below 5.73.16, or is 6.0.0 through 6.7.2 (not including 6.7.2)
  2. Identify collections with revisions enabled
    Review your collection configuration files in content/collections/ or via the Control Panel under Collections > [Collection Name] > revisions settings
    Affected if Any collection has revisions enabled and the Statamic version is in the vulnerable range
  3. Review collection permission assignments
    Check user roles and permissions in the Control Panel under Users > Roles, or inspect the roles YAML/JSON configuration files in users/roles/
    Affected if Users exist with access to the Control Panel who should NOT have edit permissions for collections that have revisions enabled (vulnerability allows unauthorized revision access)
  4. Verify revision controller authorization behavior
    Inspect the revision controller code (typically in vendor/statamic/cms/src/Http/Controllers/CP/Revisions or similar path) for proper authorization checks before listing or creating revisions
    Affected if The controller does not verify the user has edit permissions for the specific collection before allowing revision operations

You are affected if running Statamic version 5.x below 5.73.16 or 6.x below 6.7.2 AND you have collections with revisions enabled where some authenticated Control Panel users should not have edit access to those collections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.73.16 / 6.7.2 or later
Fixed in 5.73.166.7.2
Interim mitigation

Upgrade Statamic to version 5.73.16 or 6.7.2 or later to apply the vendor patch that enforces proper authorization checks on revision controllers.

Recommended fix High confidence

Statamic v5.x → 5.73.16+ or Statamic v6.x → 6.7.2+

  1. 1. Identify the currently installed Statamic version by checking your composer.json or running `php artisan statamic:version`
  2. 2. If running Statamic v5.x (< 5.73.16): Run `composer update statamic/cms --with-all-dependencies` to upgrade to version 5.73.16 or later
  3. 3. If running Statamic v6.x (>= 6.0.0, < 6.7.2): Run `composer update statamic/cms --with-all-dependencies` to upgrade to version 6.7.2 or later
  4. 4. After upgrading, clear the application cache with `php artisan cache:clear`
  5. 5. Verify the upgrade was successful by checking the version with `php artisan statamic:version`
  6. 6. Review the changes in the Statamic release notes to ensure no custom code is affected
Caveat Review Statamic v5.73.16 and v6.7.2 release notes for any breaking changes; minor version updates typically have minimal impact

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Statamic Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33887 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33887 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data