Concrete CMS is vulnerable to CSRF via Backend\File::approveVersion
Concrete CMS 9.5.0 and below is vulnerable to CSRF via Backend\File::approveVersion. Victim with edit_file_contents permission is CSRF'd into publishing an attacker-chosen previously-uploaded version (downgrade to an older version of a file, or activation of a co-editor's unpublished version). Thanks Winston Crooker for reporting.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | concrete5/concrete5 | < 9.5.1 | 9.5.1 |
References
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N- Weakness (CWE)
CWE-352- Platform
- Composer
- Package
concrete5/concrete5- Disclosed
- 26.05.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-xjg6-5v39-v7fc - CC BY 4.0
Vulnerability history: concrete5/concrete5
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 121
- First → latest
- 10.2021 06.2026
- Without a fix
- 10
- Exploited in attacks
- 0
Severity breakdown
- Critical 2
- High 16
- Medium 65
- Low 38
Disclosures per year
- 2021: 2
- 2022: 18
- 2023: 21
- 2024: 21
- 2025: 5
- 2026: 54
-
Concrete CMS is vulnerable to CSRF via Backend\File::approveVersion this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.