# CVE-2026-7025: Typecho Ping Back Service Endpoint Service.php sendPingHandle server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in Typecho's pingback service to access internal resources.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-8rj6-jxxp-67pg

## What is CVE-2026-7025?

CVE-2026-7025 is a medium-severity server-side request forgery vulnerability in Typecho, published on 26 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Typecho up to 1.3.0. This vulnerability affects the function Service::sendPingHandle of the file var/Widget/Service.php of the component Ping Back Service Endpoint. The manipulation of the argument X-Pingback/link results in server-side request forgery. The attack may be launched remotely. The exploit has been made public and could be used. Upgrading to version 1.3.1-rc is able to resolve this issue. The patch is identified as 96ccfdda4fc1e66ca04a003bf0c71d25864e6a0b. Upgrading the affected component is advised.

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

## Which versions are affected by CVE-2026-7025?


## How do I fix CVE-2026-7025?

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

## Is CVE-2026-7025 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7025 and fix it if it is affected.

What it is: CVE-2026-7025 is a medium-severity server-side request forgery vulnerability in Typecho, published on 26 Apr 2026. 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-2026-7025 exists.

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

## Sources

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

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