# CVE-2026-86307: light0011 cms cross-site request forgery

> Attackers can perform unauthorized actions on behalf of authenticated users in light0011 CMS due to missing CSRF protections.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-h595-wq86-pmx6

## What is CVE-2026-86307?

CVE-2026-86307 is a medium-severity vulnerability in light0011 cms, published on 7 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A security vulnerability has been detected in light0011 cms c774dce31c6df0055568a8d5c53d964d99be199d/f72cf46f601efb2a0618c3814cc2f61380b38930. This vulnerability affects unknown code. The manipulation leads to cross-site request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-86307?


## How do I fix CVE-2026-86307?

No fix has been published for CVE-2026-86307 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86307 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86307 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86307 and fix it if it is affected.

What it is: CVE-2026-86307 is a medium-severity vulnerability in light0011 cms, published on 7 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86307 exists.

Affected product: light0011 cms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86307/ (Markdown: https://insights.sbomify.com/CVE-2026-86307/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86307
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86307
- OSV: https://osv.dev/vulnerability/CVE-2026-86307

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86307/
Summaries are generated and may contain mistakes; the official description above is the record.