Statamic CMS up to 5.73.15/6.7.1 Edit Permission authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Statamic CMS up to 5.73.15/6.7.1. It has been classified as critical. This affects an unknown part of the component Edit Permission Handler. This manipulation causes authorization. This vulnerability is tracked as CVE-2026-33887. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability has been found in Statamic CMS up to 5.73.15/6.7.1 and classified as critical. Affected by this vulnerability is an unknown code block of the component Edit Permission Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-33887 since 03/24/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 5.73.16 or 6.7.2 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 5.73.0
- 5.73.1
- 5.73.2
- 5.73.3
- 5.73.4
- 5.73.5
- 5.73.6
- 5.73.7
- 5.73.8
- 5.73.9
- 5.73.10
- 5.73.11
- 5.73.12
- 5.73.13
- 5.73.14
- 5.73.15
- 6.7.0
- 6.7.1
Website
- Product: https://github.com/statamic/cms/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: CMS 5.73.16/6.7.2
Timeline
03/24/2026 CVE reserved03/27/2026 Advisory disclosed
03/27/2026 VulDB entry created
03/27/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-4hp7-3wxg-cv9q
Status: Confirmed
CVE: CVE-2026-33887 (🔒)
GCVE (CVE): GCVE-0-2026-33887
GCVE (VulDB): GCVE-100-354037
Entry
Created: 03/27/2026 23:46Changes: 03/27/2026 23:46 (65)
Complete: 🔍
Cache ID: 216:7B1:103
No comments yet. Languages: en.
Please log in to comment.