# CVE-2026-121940: Stonewuu ai-fusion-video before 1.3.0 IDOR via Project, Asset and Script Controllers


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-66jm-x353-x3mc

## What is CVE-2026-121940?

CVE-2026-121940 is a high-severity vulnerability in Stonewuu ai-fusion-video, published on 4 Nov 2026. 

### Official description

Stonewuu ai-fusion-video before 1.3.0 contains an insecure direct object reference vulnerability that allows authenticated users to access other users' projects by supplying unscoped object ids. Attackers can enumerate auto-increment ids on /api/project, /api/asset and /api/script handlers to read, overwrite, cascade-delete data, and add themselves as project members.

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

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


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

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

## Is CVE-2026-121940 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121940 is a high-severity vulnerability in Stonewuu ai-fusion-video, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121940 exists.

Affected product: Stonewuu ai-fusion-video. 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-121940/ (Markdown: https://insights.sbomify.com/CVE-2026-121940/index.md)
```

## Sources

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

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