CVE-2026-18425

IDOR in Concrete CMS 9.0.0 through 9.5.2 dashboard sitemap reorder (SitemapUpdate::updateDisplayOrder) allows an authenticated sitemap user to reorder arbitrary pages

Published Sep 15, 2026 CVSS 4.0 · 2.1 Low EPSS < 1% KEV · Not listed
Description
Concrete CMS 9 before 9.5.3 authorized the dashboard sitemap reorder action (Concrete\Controller\Backend\Dashboard\SitemapUpdate) using only the global access_sitemap task permission and did not check per-page edit permission before updating each page's display order. As a result, an authenticated user granted sitemap access could change the display order (cDisplayOrder) of any pages they had no rights to edit, altering the order in which those pages render in navigation, breadcrumb, and page-list output. The reorder action additionally validated no CSRF token, so the write could be triggered by a forged request. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.1 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Winston Crooker for reporting.

Analysis

AI-generated

Technical impact

Concrete CMS versions 9.0.0 through 9.5.2 allow an authenticated user with broad sitemap access to reorder any page’s display order. The backend endpoint, SitemapUpdate::updateDisplayOrder, relies only on a global sitemap flag and skips checking each target page’s edit permissions. Additionally, the action omits a CSRF token, so a forged request can trigger the write. The result is that a user who cannot edit certain pages can still change the order in which those pages appear in navigation menus, breadcrumbs, and page‑list output, potentially misleading visitors or altering the perceived structure of the site. The vulnerability does not grant code execution or data exfiltration but does expose a flaw in access control semantics for page ordering.

Affected Systems

Any installation of Concrete CMS version 9.0.0 up to and including 9.5.2 that has enabled the dashboard sitemap functionality. All such sites must be evaluated for the presence of the vulnerable reorder endpoint.

Risk and Exploitability

The CVSS score of 2.1 indicates a low impact rating. The EPSS score is reported as below 1 %, meaning the exploitation probability is very low. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires an authenticated user with sitemap permission, so it is constrained to internal or compromised accounts. Because the lack of a CSRF token allows a forged request, an attacker who can trick the victim into accessing a crafted URL could trigger the action from a remote context, but still must possess the necessary permission. Given the limited scope and low likelihood, the overall risk is minimal, but the issue demonstrates a weakness in authorization checks that can be abused by privileged users.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Concrete CMS to version 9.5.3 or later, which corrects the access and CSRF checks.
  • Restrict the sitemap permission to trusted accounts only, limiting the pool of users who can trigger the reorder action.
  • Ensure that all admin endpoints require a valid CSRF token; if the platform does not enforce this, implement a CSRF guard as a temporary mitigant.
  • Review page permission settings to confirm that only intended users have edit rights, reducing the impact of any future ordering or similar flaws.

Generated by OpenCVE AI on September 20, 2026 at 11:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:concretecms:concrete_cms:*:*:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 2.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Concretecms
Concretecms concrete Cms
Vendors & Products Concretecms
Concretecms concrete Cms
Type Values Removed Values Added
Description Concrete CMS 9 before 9.5.3 authorized the dashboard sitemap reorder action (Concrete\Controller\Backend\Dashboard\SitemapUpdate) using only the global access_sitemap task permission and did not check per-page edit permission before updating each page's display order. As a result, an authenticated user granted sitemap access could change the display order (cDisplayOrder) of any pages they had no rights to edit, altering the order in which those pages render in navigation, breadcrumb, and page-list output. The reorder action additionally validated no CSRF token, so the write could be triggered by a forged request. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.1 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Winston Crooker for reporting.
Title IDOR in Concrete CMS 9.0.0 through 9.5.2 dashboard sitemap reorder (SitemapUpdate::updateDisplayOrder) allows an authenticated sitemap user to reorder arbitrary pages
Weaknesses CWE-352
CWE-862
References
Metrics cvssV4_0

{'score': 2.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

  • CWE-862

    Missing Authorization

Sources

Status
PUBLISHED
Assigner
ConcreteCMS
Published
Updated
Sep 20, 2026, 12:45 AM
Reserved
Jul 30, 2026, 6:16 PM
Status
Analyzed
Published
Sep 15, 2026, 8:17 PM
Modified
Sep 21, 2026, 5:51 PM