/

CVE-2026-85379

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in light0011 CMS Query Builder

CVE-2026-85379

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Unauthorized database access, data disclosure, and data manipulation

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A SQL injection vulnerability in the light0011 CMS Query Builder allows attacker-controlled chapter search content to alter database queries. Because the affected search function is remotely reachable, an unauthenticated or otherwise low-privilege attacker may be able to access or modify data, depending on application permissions and database configuration.

Affected context

The vulnerability occurs in the light0011 CMS chapter-search workflow, specifically in ChapterModel::searchChapter within App/Home/Controller/ChapterController.class.php. It becomes risky when externally supplied content is incorporated into Query Builder statements without reliable parameter binding or equivalent query controls. The precise impact depends on the database account privileges and the application's exposure of the affected endpoint.

Exploit preconditions

  • Attack surface: A remotely accessible chapter-search or related CMS request
  • Required access: Potentially no authentication if the affected function is publicly reachable; otherwise, access to the relevant CMS feature
  • Trigger point: Processing of attacker-controlled content by ChapterModel::searchChapter
  • Why exploitation is possible: Input may influence SQL syntax when query construction does not consistently separate data from database commands

Why this happens

The underlying bug is an injection flaw in database query construction. Untrusted content is allowed to reach a Query Builder operation without sufficient parameterization, escaping, or structured query handling. This maps primarily to CWE-89, Improper Neutralization of Special Elements used in an SQL Command. CWE-74 is also relevant because the broader issue is inadequate neutralization of control syntax in an interpreted language.

Potential impact

  • An attacker may read sensitive records from the application database.
  • An attacker could alter, insert, or delete database content if the database account permits it.
  • An attacker may bypass application-level data access restrictions.
  • An attacker could affect CMS content, user records, or operational data.
  • Database availability could be reduced through disruptive queries or data tampering.

General mitigation guidance

Mitigation generally focuses on ensuring that all database operations use parameterized queries, prepared statements, or Query Builder APIs that preserve data and SQL structure as separate concerns. Input validation and allowlisting can reduce unexpected content but should not replace parameterization. Database credentials should follow least privilege, with separate accounts and restricted write or administrative capabilities where practical. Error responses should avoid exposing database details, and untrusted request data should not be treated as query fragments. Secure defaults, centralized data-access helpers, and review of related search functions can reduce recurrence.

How teams detect issues like this

Detection approaches include static analysis for string concatenation, interpolation, or raw SQL fragments involving request parameters; code review checks confirming parameter binding at every database boundary; and runtime monitoring for anomalous query errors, unusual search patterns, or unexpected database access. Policy enforcement can require approved parameterized database APIs and reject raw query construction in application code. Automated security review tools may help identify similar injection paths, but findings should be validated against actual data-flow and query behavior.

Sources

SourceLink
github.comgithub.com/light0011/cms/
github.comgithub.com/light0011/cms/issues/7
vuldb.comvuldb.com/cve/CVE-2026-85379
vuldb.comvuldb.com/submit/894788
vuldb.comvuldb.com/vuln/398533
vuldb.comvuldb.com/vuln/398533/cti

Frequently asked

questions

Yes. The reported attack surface is remote, although practical exploitability

depends on whether the affected chapter-search functionality is publicly

reachable and what access controls surround it.

Not necessarily. If the endpoint is exposed without authentication, an attacker

may only need network access. In protected deployments, the attacker would

need credentials or access to the relevant CMS feature.

Use parameterized queries or a Query Builder configuration that binds user

input strictly as values rather than allowing it to become SQL syntax.

Centralize database access, enforce parameterization through code-review and

CI policies, apply least-privilege database accounts, and test externally

supplied search fields for injection behavior.

Find out what's already
exploitable in your codebase.