# CVE-2025-14202: Cross-Site Request Forgery (CSRF) Leading to Account Takeover via SVG File Upload

> Attackers can upload malicious SVGs to execute JavaScript in admin browsers, stealing CSRF tokens to change passwords and take over accounts.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:L/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Dec 2025
- **Updated:** 18 Dec 2025
- **Also known as:** GHSA-cpg4-p69m-3fq5

## What is CVE-2025-14202?

CVE-2025-14202 is a high-severity cross-site scripting vulnerability in LinkDing, published on 17 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the file upload at bookmark + asset rendering pipeline allows an attacker to upload a malicious SVG file with JavaScript content. When an authenticated admin user views the SVG file with embedded JavaScript code of shared bookmark, JavaScript executes in the admin’s browser, retrieves the CSRF token, and sends a request to change the admin's password resulting in a full account takeover.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2025-14202 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14202 is a high-severity cross-site scripting vulnerability in LinkDing, published on 17 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-14202 in the wild and no public exploit code.

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

## Sources

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

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