# CVE-2025-71421: UVdesk core-framework before 1.1.7 Privilege Escalation via editAgent

> Agents with management privileges can escalate to administrator by modifying their own role via the editAgent endpoint.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-hvr3-jhx6-xw68

## What is CVE-2025-71421?

CVE-2025-71421 is a high-severity vulnerability in uvdesk community-skeleton, published on 21 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

UVdesk core-framework before 1.1.7 contains an improper privilege management vulnerability in the editAgent endpoint that allows agents with agent-management privilege to escalate their own role to administrator. Attackers can submit their own account identifier with a role parameter set to ROLE_ADMIN to gain full administrative control over agents, tickets, and mail configuration.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-71421?


## How do I fix CVE-2025-71421?

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

## Is CVE-2025-71421 being exploited?

There is no known exploitation of CVE-2025-71421 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71421 and fix it if it is affected.

What it is: CVE-2025-71421 is a high-severity vulnerability in uvdesk community-skeleton, published on 21 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-71421 in the wild and no public exploit code.

Affected product: uvdesk community-skeleton. 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-2025-71421/ (Markdown: https://insights.sbomify.com/CVE-2025-71421/index.md)
```

## Sources

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

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