CVE-2026-68531
Last modified
CVE-2026-68531 is a low-severity vulnerability rated 2.1/10 on the CVSS scale. 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 page list, allowing an authenticated user with editor-level or higher privileges to submit a crafted search containing many single-character wildcards. Because the keyword input was placed into the LIKE clause without neutralizing its wildcard metacharacters, a short request could force the database to evaluate every row and perform a full-table scan, and repeated or wildcard-dense searches could sustain elevated database CPU and I/O, degrading responsiveness for other users on large installations. 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:N/VA:L/SC:N/SI:N/SA:N. EPSS estimates a 0.25% chance of exploitation in the next 30 days.
Description
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 page list, allowing an authenticated user with editor-level or higher privileges to submit a crafted search containing many single-character wildcards. Because the keyword input was placed into the LIKE clause without neutralizing its wildcard metacharacters, a short request could force the database to evaluate every row and perform a full-table scan, and repeated or wildcard-dense searches could sustain elevated database CPU and I/O, degrading responsiveness for other users on large installations. 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:N/VA:L/SC:N/SI:N/SA:N. Thanks noivan for reporting.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Concrete CMS | Concrete CMS | >= 9.0.0, <= 9.5.2 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-68531?
How severe is CVE-2026-68531?
How do I fix CVE-2026-68531?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-68526Concrete CMS before 9.5.3 did not validate an anti-CSRF toke…5.3
- CVE-2026-68527Concrete CMS versions 8.3.0 through 9.5.2 are vulnerable to …5.9
- CVE-2026-68528Concrete CMS RSS Displayer block below version 9.5.3 render…6
- CVE-2026-68529Concrete CMS 9.0.0 through 9.5.2 was missing an authorizatio…2.1
- CVE-2026-6853Improper restriction of excessive authentication attempts vu…9.8
- CVE-2026-68530Concrete CMS 9 through 9.5.2 did not perform an authorizatio…2.1
- CVE-2026-68532Concrete CMS 9.0.0 to dashboard group type controller did no…2.3
- CVE-2026-68533Concrete CMS below 9.5.3 conversation attachment uploaded en…2.3
- CVE-2026-68534Concrete CMS before 9.5.3 rendered Express entry labels as r…2.3
- CVE-2026-68535Concrete CMS Area API's block-create endpoint in versions 9.…5.1
- CVE-2026-68536Server-Side Request Forgery / Local File Inclusion in Apache…
- CVE-2026-6854The My Calendar – Accessible Event Manager plugin for WordPr…7.5
Are you affected by CVE-2026-68531?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
