# CVE-2025-52919: File upload in RPS

> Attackers can upload invalid certificates due to insufficient validation in Yealink RPS, potentially bypassing security controls.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A: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 Jun 2025
- **Updated:** 28 Jul 2025
- **Also known as:** GHSA-h483-pm62-h98h

## What is CVE-2025-52919?

CVE-2025-52919 is a medium-severity vulnerability in Yealink RPS, published on 21 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Yealink RPS before 2025-05-26, the certificate upload function does not properly validate certificate content, potentially allowing invalid certificates to be uploaded.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2025-52919 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52919 is a medium-severity vulnerability in Yealink RPS, published on 21 Jun 2025. 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-52919 exists.

Affected product: Yealink RPS. 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-52919/ (Markdown: https://insights.sbomify.com/CVE-2025-52919/index.md)
```

## Sources

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

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