Concrete CMS 9.5.0 and below emits a CSRF token in the localavailableupdate.php view ($token->output('doupdate')) but the corresponding doupdate() method in concrete/controllers/singlepage/dashboard/system/update/update.php never calls $this->token->validate('doupdate'). 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 DIRCOREUPDATES. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 7.5 with 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. Thanks https://github.com/maru1009 for reporting.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/8xxx/CVE-2026-8428.json",
"cna_assigner": "ConcreteCMS",
"cwe_ids": [
"CWE-352",
"CWE-829"
]
}{
"cpe": "cpe:2.3:a:concretecms:concrete_cms:*:*:*:*:*:*:*:*",
"source": [
"AFFECTED_FIELD",
"CPE_RANGE"
],
"extracted_events": [
{
"introduced": "5.0"
},
{
"last_affected": "9.5.0"
},
{
"introduced": "0"
},
{
"fixed": "9.5.1"
}
]
}