Skip to main content
VulnerabilityPublished Updated

CVE-2026-33886: statamic cms · Information Exposure

Affects statamic cmsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 6.7.2 or 5.73.16 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.7.2, 5.73.16
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade cms and statamic/cms to 6.7.2 or 5.73.16.

Affected software

ProductAffectedFixed in
statamiccmsAffected
  • >=6.0.0.alpha.1 <6.7.2
Fixed in
  • 6.7.2
statamiccmsAffected
  • >=5.73.12 <5.73.16
Fixed in
  • 5.73.16
GitHubstatamic/cmspkg:github/statamic/cmsOther threatsAffected
  • <5.73.16
  • <6.7.2
Fixed in
  • 5.73.16
  • 6.7.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Statamic CMS to version 5.73.16 or later, or version 6.7.2 or later, where this vulnerability has been fixed. No other mitigations are specified or required once the update is applied. Patch status is confirmed fixed in these versions.

Description

Statamic is a Laravel and Git powered content management system (CMS). Starting in version 5.7.12 and prior to versions 5.73.16 and 6.7.2, a control panel user with access to Antlers-enabled fields could access sensitive application configuration values by inserting config variables into their content. This has been fixed in 5.73.16 and 6.7.2.

References

Community reviews

Loading reviews…