# CVE-2025-71420: UVdesk core-framework before 1.1.7 Authorization Bypass via Saved Reply

> Authenticated agents can bypass authorization checks to read saved replies restricted to other support groups in UVdesk core-framework.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/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:** 21 Sep 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-gvmp-wwrp-jm4j

## What is CVE-2025-71420?

CVE-2025-71420 is a medium-severity missing authorization vulnerability in uvdesk community-skeleton, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

UVdesk core-framework before 1.1.7 contains an authorization bypass vulnerability in the saved reply endpoint that allows authenticated agents to access replies restricted to other support groups. Attackers with ROLE_AGENT can enumerate saved reply identifiers and read content reserved for groups and teams they do not belong to.

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

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


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

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

## Is CVE-2025-71420 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-71420 is a medium-severity missing authorization vulnerability in uvdesk community-skeleton, published on 21 Sep 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-2025-71420 exists.

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-71420/ (Markdown: https://insights.sbomify.com/CVE-2025-71420/index.md)
```

## Sources

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

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