CVE-2026-8421: Concrete CMS 9.5.0 and below is vulnerable to CSRF on install_package() with conditional token bypass leading to RCE
Concrete CMS 9.5.0 and below contains a CSRF vulnerability in the installpackage() method of concrete/controllers/singlepage/dashboard/extend/install.php. An attacker who can cause an authenticated administrator to visit a crafted page, and who has placed or caused a package to be present under DIRPACKAGES/<handle>/, can force the installation of that package without any CSRF protection. Package installation executes the package controller's install() method as the web server user, enabling remote code execution. In order to be vulnerable, the victim must be passing canInstallPackages. 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-8421?
CVE-2026-8421 has a severity rating of high, with a CVSS score of 7.5.
What type of vulnerability is CVE-2026-8421?
CVE-2026-8421 is a Cross-Site Request Forgery (CSRF) vulnerability affecting Concrete CMS.
How do I fix CVE-2026-8421?
To fix CVE-2026-8421, update Concrete CMS to version 9.5.1 or later.
What can an attacker do with CVE-2026-8421?
An attacker can exploit CVE-2026-8421 to execute remote code on a vulnerable Concrete CMS installation via a crafted page.
Which versions of Concrete CMS are affected by CVE-2026-8421?
CVE-2026-8421 affects Concrete CMS versions 9.5.0 and below.