Typecho (<= 1.3.0) — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/typecho--1.3.0/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSun, 26 Apr 2026 08:17:46 +0000Typecho <= 1.3.0 Server-Side Request Forgery Vulnerability (CVE-2026-7025)https://feed.craftedsignal.io/briefs/2026-04-typecho-ssrf/Sun, 26 Apr 2026 08:17:46 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-04-typecho-ssrf/A server-side request forgery (SSRF) vulnerability exists in Typecho up to version 1.3.0, allowing remote attackers to manipulate the X-Pingback/link argument in the Service::sendPingHandle function to potentially make arbitrary HTTP requests.Typecho is vulnerable to a server-side request forgery (SSRF) vulnerability (CVE-2026-7025) affecting versions up to 1.3.0. The vulnerability resides in the Service::sendPingHandle function within the var/Widget/Service.php file, specifically impacting the Ping Back Service Endpoint component. An attacker can remotely trigger this vulnerability by manipulating the X-Pingback/link argument. Publicly available exploits exist, increasing the risk of exploitation. The vendor was notified but did not respond. This vulnerability allows an attacker to potentially make arbitrary HTTP requests from the server, leading to information disclosure or further compromise.

Attack Chain

  1. The attacker identifies a Typecho instance running a vulnerable version (<= 1.3.0).
  2. The attacker crafts a malicious HTTP request targeting the Pingback service endpoint.
  3. The malicious request includes a manipulated X-Pingback or link argument pointing to an attacker-controlled server or internal resource.
  4. The Service::sendPingHandle function processes the request and attempts to fetch the resource specified in the X-Pingback/link argument.
  5. Due to the SSRF vulnerability, the Typecho server makes an outbound HTTP request to the attacker-specified URL.
  6. The attacker’s server logs the incoming request from the Typecho server, confirming the SSRF vulnerability.
  7. The attacker could potentially use this SSRF vulnerability to scan internal networks, read sensitive files, or interact with internal services.
  8. Successful exploitation could lead to information disclosure, further exploitation of internal services, or denial-of-service attacks.

Impact

Successful exploitation of CVE-2026-7025 can allow an attacker to perform unauthorized actions on the internal network of the Typecho server. This includes port scanning, accessing internal services, and potentially reading sensitive data. The number of affected installations is unknown, but any Typecho instance running version 1.3.0 or earlier is vulnerable. The impact is limited to the permissions of the Typecho web server process, but can expose sensitive internal services that are not directly accessible from the internet.

Recommendation

  • Apply input validation and sanitization to the X-Pingback/link argument to prevent arbitrary URL inclusion, mitigating CVE-2026-7025.
  • Monitor web server logs for suspicious requests containing unusual URLs in the X-Pingback header, which can indicate SSRF attempts.
  • Implement network segmentation to limit the impact of potential SSRF attacks by restricting the web server’s access to internal resources.
  • Deploy the Sigma rule Detect Suspicious X-Pingback Header to identify potential SSRF attempts targeting the Pingback service.
  • Audit outbound network connections from the web server to detect unauthorized access to internal resources as a result of SSRF.
]]>mediumadvisoryssrfcve-2026-7025typecho