# CVE-2025-61768: Kuno CMS Vulnerable to Server-Side Request Forgery (SSRF) via Unsafe SVG Upload

> An administrator can upload a malicious SVG file to trigger server-side requests, enabling internal network probing and information disclosure.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:L/SC:L/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:** 6 Oct 2025
- **Updated:** 7 Oct 2025
- **Also known as:** GHSA-4f5f-2c49-5mwm

## What is CVE-2025-61768?

CVE-2025-61768 is a medium-severity server-side request forgery vulnerability in xuemian168 kuno, published on 6 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

KUNO CMS is a fully deployable full-stack blog application. In versions prior to 1.3.15, an SSRF (Server-Side Request Forgery) vulnerability exists in the Media module of the Kuno CMS administrative panel. A logged-in administrator can upload a specially crafted SVG file containing an external image reference, causing the server to initiate an outgoing connection to an arbitrary external URL. This can lead to information disclosure or internal network probing. Version 1.3.15 contains a fix for the issue.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2025-61768 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61768 is a medium-severity server-side request forgery vulnerability in xuemian168 kuno, published on 6 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61768 exists.

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

## Sources

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

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