Concrete CMS 9.0.0 through 9.5.2 is vulnerable to Insecure direct object reference (IDOR) in the Express saved search preset delete and edit dialogs . An authenticated user holding only view permission on a single Express entity could therefore permanently delete, with no undo, or rename saved search presets owned by Express entities for which they had no permission, and a renamed preset name was displayed back to users of the targeted entity, enabling defacement or social engineering. 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:L/SC:N/SI:N/SA:N. Thanks Yalguun Tumenkhuu ( fg0x0 ) for reporting.
CVE-2026-18423
This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- 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.1
- EG Score
- 2.1(medium)
- EG Risk
- 10(Track)EG Risk 10/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 computedSeverity21% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 16, 2026
References (1)
- ff5b8ace-8b95-4078-9743-eac1ca5451dehttps://documentation.concretecms.org/developers/introduction/version-history/953-release-notes
Vendor Advisories for CVE-2026-18423(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 10× in last 7d / 10× 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-20 01:12 UTCEG score recompute
- 2026-09-20 01:12 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-16 19:23 UTCEG score recompute
- 2026-09-16 19:23 UTCGHSA enrichment
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-15 20:39 UTCEG score recompute
- 2026-09-15 19:48 UTCEG score recompute
- 2026-09-15 19:33 UTCEG score recompute
- 2026-09-15 19:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
Frequently asked(5)
What is CVE-2026-18423?
When was CVE-2026-18423 disclosed?
Is CVE-2026-18423 actively exploited?
What is the CVSS score of CVE-2026-18423?
How do I remediate CVE-2026-18423?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18423
Is Your Infrastructure Affected by CVE-2026-18423?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.