---
id: "CVE-2026-119654"
kind: "vulnerability"
aliases: ["CVE-2026-119654"]
title: "DataCap: any logged-in user can grant themselves administrator role"
severity: "high"
cvss: 8.8
epss: null
exploited: false
status: "open"
category: "other"
products: [{"name": "DataCap", "fixed": [], "affected": "<= 2025.1.1", "ecosystem": "vendor"}]
ecosystems: []
tags: ["datacap", "java", "other", "privilege-escalation", "self-hosted"]
not_affected_if: ["auth-required", "registration-closed"]
published_at: "2026-10-30T15:16:49+00:00"
first_seen_at: "2026-10-30T15:31:10+00:00"
updated_at: "2026-10-30T15:34:55+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119654", "first_seen_at": "2026-10-30T15:31:10+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-30T15:34:55+00:00"}]
---

# DataCap: any logged-in user can grant themselves administrator role

DataCap through 2025.1.1 lacks an authorization check on its administrative role and menu management APIs. An authenticated user, including a self-registered one, can call PUT /api/v1/user/allocationRole to make themselves an administrator and take full control of the instance.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:DataCap affected <= 2025.1.1 fixed ?

## How to check

- Run DataCap 2025.1.1 or earlier? You are affected (check the version in the UI or the server jar/tarball name).
- Any logged-in account can PUT /api/v1/user/allocationRole with its own userId and an admin role code; the endpoint has no @PreAuthorize. Review accounts and roles for unexpected admins.
- The same gap is on /api/v1/role and /api/v1/menu (create/update, bind menus), so check for unfamiliar roles.
- Restrict the instance to trusted users and check whether self-registration is on.

## Timeline

- 2026-10-30T15:31:10+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119654
- 2026-10-30T15:34:55+00:00 analyst — Read VulnCheck advisory and reporter write-up (static review only, no runtime test, no PoC published). Affected DataCap <= 2025.1.1 (repo devlive-community/metaforge). No vendor advisory or fixed version found; maintainer issue #969 not readable here. Nothing verified.

## Documents

- [advisory] VulnCheck: DataCap through 2025.1.1 allocationRole missing authorization https://www.vulncheck.com/advisories/datacap-through-2025.1.1-privilege-escalation-via-allocationrole-missing-authorization
- [describes] Reporter write-up: DataCap allocationRole missing authorization (static review, not runtime-tested) https://hackmd.io/@hieuPenguinnn/metaforge-datacap-allocation-role-missing-authz-privilege-escalation

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_