CVE-2026-8427
Concretecms Concrete CMS cross-site request forgery (CSRF)
- Published21 May 2026
Description
Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file removeFavoriteFolder($id). The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 2.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Yonatan Drori (Tenzai) for reporting.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-8427 being actively exploited?
CVE-2026-8427 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.20%.
How severe is CVE-2026-8427?
CVE-2026-8427 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.20% probability of exploitation.
Which products are affected by CVE-2026-8427?
Affected products include Concretecms Concrete CMS.
How do I fix CVE-2026-8427?
Upgrade affected software to a fixed version, for example Concretecms Concrete CMS 9.5.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-8427 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.