dbcve.org
StatamicApplication

CVE-2026-33882

MEDIUM · 6.5 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 →
71/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, the markdown preview endpoint could be manipulated to return augmented data from arbitrary fieldtypes. With the users fieldtype specifically, an authenticated control panel user could retrieve sensitive user data including email addresses, encrypted passkey data, and encrypted two-factor authentication codes. 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's markdown preview endpoint allowed authenticated control panel users to manipulate fieldtype data retrieval. By specifying the 'users' fieldtype, attackers could extract sensitive user data including email addresses, encrypted passkey credentials, and encrypted two-factor authentication codes. This is a data exposure vulnerability via direct object reference in the preview functionality.

MitigationUpgrade Statamic to version 5.73.16 or 6.7.2 or later to patch the markdown preview endpoint vulnerability. Review user access logs for any suspicious use of the preview functionality.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Verify Statamic version
    Locate your Statamic installation and check the version number in the composer.json file, control panel footer, or by running `php artisan statamic:version` from the project root
    Affected if The installed version is less than 5.73.16 OR greater than or equal to 6.0.0 but less than 6.7.2
  2. Confirm control panel access
    Identify users who have authenticated access to the Statamic control panel, particularly those with Editor, Author, or Contributor roles
    Affected if Any authenticated user can access the markdown preview endpoint and exploit the vulnerability
  3. Inspect application logs for preview requests
    Review Statamic application logs (typically in storage/logs/) for any requests to endpoints containing '/preview' or 'markdown' that include the 'users' fieldtype parameter
    Affected if Logs show requests to the preview endpoint with 'users' fieldtype or requests accessing user data fields
  4. Audit content blueprints for users fieldtype
    Examine your Statamic content blueprints (in resources/blueprints/) to see if any fields are configured with the 'users' fieldtype
    Affected if Blueprints contain 'users' fieldtype fields that could be targeted through the preview endpoint

Your environment is affected if the installed Statamic version falls within the vulnerable ranges AND the control panel is accessible to authenticated users who could exploit the preview endpoint.

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 patch the markdown preview endpoint vulnerability. Review user access logs for any suspicious use of the preview functionality.

Recommended fix High confidence

Statamic 5.73.16 or 6.7.2

  1. Backup your Statamic site and database before upgrading
  2. Update your composer.json to require the fixed version: for Statamic 5.x use "statamic/cms": "5.73.16" or for Statamic 6.x use "statamic/cms": "6.7.2"
  3. Run `composer update statamic/cms --no-interaction` to install the fixed version
  4. Clear any application caches with `php artisan cache:clear`
  5. Verify the upgrade was successful by checking the Statamic version with `php artisan statamic:version`
  6. Test the markdown preview functionality in a staging environment before deploying to production

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

Fix this in Statamic Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33882 — 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-33882 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