Concrete CMS versions
Concrete CMS: update to 9.5.7. 8 and older no longer get fixes.
Data: .
Which Concrete CMS branch to run
The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.
| Branch | Status | Newest safe release | Upgrade to |
|---|---|---|---|
| 9137 CVE records that this page reads | Fixes, no end date announced | 9.5.7 | 9.5.7 (this branch) |
| 812 CVE records that this page reads | Ended on 5 August 2025 | None, the branch has ended | 9.5.7 (move to 9) |
| 5.7 | Ended on 23 October 2019 | None, the branch has ended | 9.5.7 (move to 9) |
| 5.6 | Ended on 26 February 2019 | None, the branch has ended | 9.5.7 (move to 9) |
Exploited, or likely to be
CVE records for Concrete CMS that CISA lists as exploited, that have a public exploit, or that EPSS rates 0.50 or more, with the releases that fix each where the record names them. 1 of the 2 records shown names one.
| Record | Signs of exploitation | Fixed in |
|---|---|---|
| CVE-2026-6826Concrete 9.5.0 and below has file usage disclosure via missing permission check in Usage controller6.9 Medium · published 21 May 2026 | Metasploit module | The record names no fixed release for 9. |
| CVE-2025-8573Concrete CMS 9 through 9.4.2 is vulnerable to Stored XSS from Home Folder on Members Dashboard page2.0 Low · published 5 August 2025 | Exploit-DB entry | Fixed in 9.4.3 |
What this page counts
The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.
This page reads 138 CVE records that the CVE Numbering Authorities ConcreteCMS and redhat (as the CVE List names them) published and that name Concrete CMS. The fixes are from the 137 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.
No release of a branch that has ended is called safe here.
Some records give a range that starts in an older branch and ends in a newer one. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the older branches it runs across. Only a range that runs across branches that have all ended is placed: a range that reaches a branch that still gets fixes would name that branch's newest release as affected, which a project that also fixes its older branches does not mean. Such a record is named at the end of the page.
1 record is not placed on a branch, so no branch or release row counts it: CVE-2011-3183.
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)