# CVE-2025-15414: go-sonic Theme Fetching API git_fetcher.go FetchTheme server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the go-sonic library's theme fetching API to access internal resources.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jan 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-wcrf-5vr8-vwjp

## What is CVE-2025-15414?

CVE-2025-15414 is a medium-severity server-side request forgery vulnerability in go-sonic sonic, published on 1 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw has been found in go-sonic sonic up to 1.1.4. The affected element is the function FetchTheme of the file service/theme/git_fetcher.go of the component Theme Fetching API. Executing a manipulation of the argument uri can lead to server-side request forgery. The attack may be launched remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2025-15414 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15414 is a medium-severity server-side request forgery vulnerability in go-sonic sonic, published on 1 Jan 2026. 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-15414 exists.

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

## Sources

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

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