GHSA-gcqf-5x9f-hq7f CVE-2026-33886
Statamic's sensitive configuration values are exposed to content editors via Antlers-enabled fields
- Severity
- 6.5 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.23%
- Chance of exploitation in the next 30 days. Higher than 14.17% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
5.73.16- Upgrade statamic/cms to this version or later
Description
Impact
A control panel user with access to Antlers-enabled fields could access sensitive application configuration values by inserting config variables into their content.
Patches
This has been fixed in 5.73.16 and 6.7.2.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| statamic/cms | >= 5.73.12, < 5.73.16 |
5.73.16 |
| statamic/cms | >= 6.5.0, < 6.7.2 |
6.7.2 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
statamic/cms Packagist → 5.73.16
- composer
composer require statamic/cms:^5.73.16
Severity breakdown
CVSS 3.1 6.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-vx89-p3j7-8xqc Statamic: Stored Cross-Site Scripting in Automagic Form Notification Email Template | Medium | Also affects statamic/cms |
| GHSA-qhr7-v3xp-vw9m Statamic: Missing file upload validation on frontend forms allows uploading disallowed file types | Medium | Also affects statamic/cms |
| GHSA-qh8c-7588-qfrv Statamic: Missing authorization on navigation endpoint allows disclosure of restricted entries | Medium | Also affects statamic/cms |
| GHSA-j2vp-f2pv-5rj4 Statamic: Unsafe method invocation via Antlers template resolution allows data destruction | Medium | Also affects statamic/cms |
| GHSA-93qh-5269-9wcf Statamic: Account takeover via OAuth email matching without email-verification check | High | Also affects statamic/cms |
| GHSA-225x-3jhx-wh4q Statamic: Missing authorization on Control Panel endpoint allows disclosure of user existence | Medium | Also affects statamic/cms |
| GHSA-jppw-r5j3-xf7x Statamic CMS exposes two-factor recovery codes through dynamic Antlers rendering | Medium | Also affects statamic/cms |
| GHSA-7mqq-4v55-88gh Statamic CMS's incorrect authorization lets view-only users submit Live Preview content reserved for editors | Low | Also affects statamic/cms |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor