Quick answers
- Is CVE-2026-18425 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18425 being exploited in the wild.
- How severe is CVE-2026-18425?
- Low severity, with a CVSS score of 2.7, published 15 September 2026.
- Which products and versions are affected?
- Concrete CMS 9 before 9.5.3.
- Is there a fix for CVE-2026-18425?
- A patch was published on 2026-09-15: Fixed in version 9.5.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18425 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-18425?
- Check whether you run Concrete CMS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass in the Concrete\Controller\Backend\Dashboard\SitemapUpdate action. The controller checks only the global access_sitemap task permission before allowing page reorder operations, but fails to validate per-page edit permissions for individual pages being reordered. Additionally, the action does not validate CSRF tokens, enabling attackers to trigger reorder requests via forged cross-site requests. An authenticated user with sitemap access can modify the cDisplayOrder field of any page, regardless of their edit permissions for that page. The vulnerability affects Concrete CMS 9 before version 9.5.3, and patches are available in 9.5.3 and later.
Affected products
- Concrete CMS Concrete CMS 9 before 9.5.3
Timeline
- 2026-09-15: disclosed
- 2026-09-15: patched: Fixed in version 9.5.3