CVE-2026-68531: Concrete CMS 9 before 9.5.3 did not escape SQL LIKE wildcard characters in the keyword search filters used by the file manager, file folders, and
Source GCVE Database
Not known to be exploited · CVSS 2.1 Low · fixed in 9.5.3 : update affected systems when convenient.
Data as of 30 Oct 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.5.3
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
AI-suggested
A fix is available in Concrete CMS version 9.5.3. Users should upgrade to version 9.5.3 or later to remediate this vulnerability. No other mitigation actions are indicated by the vendor advisory.
Description
Concrete CMS versions prior to 9.5.3 do not properly escape SQL LIKE wildcard characters in keyword search filters used by the file manager, file folders, and page list. This allows authenticated users with editor-level or higher privileges to craft searches that cause the database to perform full-table scans, leading to elevated CPU and I/O usage and degraded responsiveness on large installations. The vulnerability has a low severity rating and does not involve remote code execution or data disclosure.