Quick answers
- Is CVE-2026-86305 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86305 being exploited in the wild.
- How severe is CVE-2026-86305?
- High severity, with a CVSS score of 7.3, published 7 September 2026.
- Which products and versions are affected?
- light0011 cms commit f72cf46f601efb2a0618c3814cc2f61380b38930 and earlier.
- Is there a fix for CVE-2026-86305?
- 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-86305 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86305?
- 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 an unrestricted file upload in the Upload::upload() function (ThinkPHP/Library/Think/Upload.class.php lines 17-31) used by multiple controllers including the unauthenticated Home/User upload action (App/Home/Controller/UserController.class.php:60-74). The root cause is that the application sets only the rootPath parameter while relying on ThinkPHP's permissive defaults for mimes=[], exts=[], and maxSize=0; validation checks at lines 285-305 and 342-360 allow all file types when these restrictions are empty. The attack is remotely exploitable without authentication; an attacker can upload arbitrary files via POST multipart requests. On deployments where the upload directory is web-accessible and PHP execution is enabled, this results in unauthenticated remote code execution. No patch has been released; the project uses a rolling release model and has not responded to the early security report.
Affected products
- light0011 cms commit f72cf46f601efb2a0618c3814cc2f61380b38930 and earlier
Timeline
- 2026-07-18: disclosed: Issue reported on GitHub
- 2026-09-07: advisory: CVE-2026-86305 published