CVE Catalog

CVE-2026-8428

HighCVSS 8.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.13%

3th percentile - higher than 3% of all known CVEs

Summary

Concrete CMS 9.5.0 and below emits a CSRF token in the local_available_update.php view, but the do_update() method does not validate it. An attacker can exploit this to perform a CSRF attack that updates the CMS to an attacker-specified version.

Risk Assessment

The risk involves an attacker remotely controlling the CMS update process, potentially leading to installation of a malicious version and full system compromise.

Recommendation

Immediately update to version 9.5.1 or later, which includes proper CSRF token validation.

Other vulnerabilities in Concrete CMS

See all
Original NVD description (English source)

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. 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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS