Quick answers
- Is CVE-2026-85379 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85379 being exploited in the wild.
- How severe is CVE-2026-85379?
- High severity, with a CVSS score of 7.3, published 4 September 2026.
- Which products and versions are affected?
- light0011 cms commit c774dce31c6df0055568a8d5c53d964d99be199d and f72cf46f601efb2a0618c3814cc2f61380b38930.
- Is there a fix for CVE-2026-85379?
- 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-85379 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-85379?
- Check whether anything you run is named in the advisory. 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 classic SQL injection in the ChapterModel::searchChapter function and related search handlers in ChapterController.class.php. The vulnerable code constructs raw SQL WHERE clauses using string interpolation of user-supplied POST and GET parameters (content and tag fields) without parameterized queries or prepared statements. An unauthenticated attacker can supply SQL boolean predicates (e.g., "notfound' OR 1=1 OR 'x'='y") in the search field to alter query logic and extract all database records or execute arbitrary SQL. The attack requires only network access to the web application and no authentication. The vendor was notified via issue report but has not responded or provided a patch.
Affected products
- light0011 cms commit c774dce31c6df0055568a8d5c53d964d99be199d and f72cf46f601efb2a0618c3814cc2f61380b38930
Timeline
- 2026-07-18: disclosed: Vulnerability reported on GitHub issue #7
- 2026-09-04: advisory: CVE-2026-85379 published on NVD