# CVE-2025-2516: Use of a weak cryptographic key in the signature verification process in WPS Office

> Weak cryptographic keys in WPS Office allow attackers to sign malicious components and hijack updates via man-in-the-middle attacks.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2025
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-cvv7-5999-m892

## What is CVE-2025-2516?

CVE-2025-2516 is a critical vulnerability in Kingsoft WPS Office, published on 27 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The use of a weak cryptographic key pair in the signature verification process in WPS Office (Kingsoft) on Windows allows an attacker who successfully recovered the private key to sign components.

As older versions of WPS Office did not validate the update server's certificate, an Adversary-In-The-Middle attack was possible allowing updates to be hijacked.

Weakness: CWE-326 (Inadequate Encryption Strength)

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


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

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

## Is CVE-2025-2516 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2516 is a critical vulnerability in Kingsoft WPS Office, published on 27 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2516 exists.

Affected product: Kingsoft WPS Office. 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-2516/ (Markdown: https://insights.sbomify.com/CVE-2025-2516/index.md)
```

## Sources

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

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