Quick answers
- Is CVE-2026-68531 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-68531 being exploited in the wild.
- How severe is CVE-2026-68531?
- Informational severity, with a CVSS score of 2.1, published 15 September 2026.
- Which products and versions are affected?
- Concrete CMS 9 before 9.5.3.
- Is there a fix for CVE-2026-68531?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-68531 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-68531?
- 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 a SQL wildcard injection flaw in the keyword search filters for file manager, file folders, and page list components. The search input is directly inserted into SQL LIKE clauses without escaping wildcard metacharacters (% and _), allowing an authenticated user with editor-level or higher privileges to submit crafted searches containing multiple single-character wildcards. When processed, these searches force full-table database scans instead of indexed lookups. Repeated or wildcard-dense searches can sustain elevated database CPU and I/O load, degrading system performance. The issue requires authentication and elevated privileges but poses a denial-of-service risk on large installations. The vulnerability was patched in version 9.5.3.
Affected products
- Concrete CMS Concrete CMS 9 before 9.5.3
Timeline
- 2026-09-15: disclosed