CSRF in Concrete Cms
CVE-2026-8426
Concrete CMS 9.5.0 and below does not validate a CSRF token before processing requests to /dashboard/extend/update/prepare_remote_upgrade/<remoteMPID>. An attacker who controls the remote package returned for a known marketplace item ID can overwrite the package PHP on disk and force its upgrade() method to execute in a single browser navigation. This results in remote code execution as the web server user. In order to be vulnerable, the victim must be passing canInstallPackages, victim site must be connected to the Concrete marketplace; and the attacker controls the package returned for a marketplace item ID already installed on the victim site. 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 class: CSRF (Cross-Site Request Forgery)
EPSS: 0.002 (6.6th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
Affected products
- Concrete Cms — versions 5.0
- Concretecms Concrete_cms
Weakness classification (CWE)
References
- ff5b8ace-8b95-4078-9743-eac1ca5451de (release-notes, Release Notes)
Frequently asked questions
- What is CVE-2026-8426?
- CVE-2026-8426 is a high-severity vulnerability in Concrete Cms, classified under Cross-Site Request Forgery (CSRF). CVSS score: 8.8/10. Published 2026-05-21.
- How severe is CVE-2026-8426?
- High severity. CVSS v3 base score is 8.8 out of 10.