# CVE-2026-111722: LingGuo-Drama through commit 8a6924a IDOR via /admin/v1/projects/:id API

> Attackers can access, modify, or delete other users' projects by manipulating IDs in the API due to missing ownership checks.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-4cg4-g3g8-qxpg

## What is CVE-2026-111722?

CVE-2026-111722 is a high-severity missing authorization vulnerability in LingGuoAI LingGuo-Drama, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LingGuo-Drama through commit 8a6924a contains an insecure direct object reference vulnerability that allows registered users to access other users' projects because projects.Get lacks an owner check. Self-registered attackers can iterate numeric IDs via GET, PUT and DELETE /admin/v1/projects/:id to read, overwrite, reassign or delete any user's short-drama projects.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-111722 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111722 is a high-severity missing authorization vulnerability in LingGuoAI LingGuo-Drama, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111722 exists.

Affected product: LingGuoAI LingGuo-Drama. 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-111722/ (Markdown: https://insights.sbomify.com/CVE-2026-111722/index.md)
```

## Sources

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

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