# CVE-2026-119654: DataCap through 2025.1.1 Privilege Escalation via allocationRole Missing Authorization


- **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:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-3c4r-whrm-5953

## What is CVE-2026-119654?

CVE-2026-119654 is a high-severity vulnerability in devlive-community DataCap, published on 30 Oct 2026. 

### Official description

DataCap through 2025.1.1 contains a missing authorization vulnerability that allows any authenticated user to escalate privileges by calling administrative role and menu management APIs. Attackers, including self-registered accounts, can send PUT requests to /api/v1/user/allocationRole to assign themselves the administrator role and gain full control of the instance.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-119654 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119654 is a high-severity vulnerability in devlive-community DataCap, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119654 exists.

Affected product: devlive-community DataCap. 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-119654/ (Markdown: https://insights.sbomify.com/CVE-2026-119654/index.md)
```

## Sources

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

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