# CVE-2025-9395: wangsongyan wblog backup.go RestorePost server-side request forgery

> Attackers can exploit a server-side request forgery vulnerability in wblog's RestorePost function to access internal resources or bypass security controls.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 24 Aug 2025
- **Updated:** 25 Aug 2025
- **Also known as:** GHSA-7hr8-h96w-3444

## What is CVE-2025-9395?

CVE-2025-9395 is a medium-severity server-side request forgery vulnerability in wangsongyan wblog, published on 24 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in wangsongyan wblog 0.0.1. This affects the function RestorePost of the file backup.go. Such manipulation of the argument fileName leads to server-side request forgery. It is possible to launch the attack remotely. The exploit is publicly available and might 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-9395?


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

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

## Is CVE-2025-9395 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9395 is a medium-severity server-side request forgery vulnerability in wangsongyan wblog, published on 24 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9395 in the wild and no public exploit code.

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

## Sources

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

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