Concrete CMS is Vulnerable to Cross-Site Request Forgery
Concrete CMS 9.5.0 and below emits a CSRF token in the local_available_update.php view ($token->output('do_update')) but the corresponding do_update() method in concrete/controllers/single_page/dashboard/system/update/update.php never calls $this->token->validate('do_update'). The form is rendered as a POST form, meaning the token reaches the browser, but because the controller discards it without verification, an attacker can craft a cross-site POST that triggers a core CMS update to an attacker-specified version string. In order to be vulnerable, theictim must be passing canUpgrade()anda valid update version must be present under DIR_CORE_UPDATES.
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:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N- Weakness (CWE)
CWE-352- Platform
- Composer
- Package
concrete5/concrete5- Disclosed
- 21.05.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-prxr-vjgc-2cq9 - 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 Cross-Site Request Forgery 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.