Concrete CMS before 9.5.3 did not enforce a per-page authorization check when reordering pages from the sitemap. In the sitemap Explore dashboard controller, the send_to_top and send_to_bottom reorder tasks ran after only a generic sitemap-access check; the controller loaded the page named by the attacker-controlled cNodeID parameter and changed its display order without verifying that the current user held move or arrange permission on that specific page. Because of this, an authenticated user who could reach the sitemap but had no edit or arrange rights on a given page could still move that page and alter the site's global navigation order. 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 Andrew Gonzalez for reporting.
CVE-2026-81922
Score 2.7 from GitHub Security Advisory (severity: LOW) published 2026-09-15. NVD baseline CVSS 2.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.7
- EG Score
- 2.7(high)
- EG Risk
- 12(Track)EG Risk 12/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity27% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 18, 2026
References (1)
- ff5b8ace-8b95-4078-9743-eac1ca5451dehttps://documentation.concretecms.org/developers/introduction/version-history/953-release-notes
Vendor Advisories for CVE-2026-81922(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 20× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 18:11 UTCEG score recompute
- 2026-09-24 18:11 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 17:00 UTCEG score recompute
- 2026-09-21 17:00 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 15:49 UTCEG score recompute▲ 0.60
- 2026-09-18 15:48 UTCGHSA enrichment
- 2026-09-18 15:43 UTCNVD updateCVSS v3 → 2.7
- 2026-09-16 19:23 UTCEG score recompute
- 2026-09-16 19:23 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 20:41 UTCEG score recompute
- 2026-09-15 19:32 UTCEG score recompute
- 2026-09-15 19:00 UTCEG score recompute
- 2026-09-15 18:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-81922?
When was CVE-2026-81922 disclosed?
Is CVE-2026-81922 actively exploited?
What is the CVSS score of CVE-2026-81922?
How do I remediate CVE-2026-81922?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81922
Is Your Infrastructure Affected by CVE-2026-81922?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.