Typecho before 1.3.1-rc contains a server-side request forgery vulnerability in the XML-RPC pingback.ping method where checkSafeHost() validates a hostname's resolved IP once but the subsequent outbound request performs an independent DNS resolution, creating a TOCTOU window exploitable via DNS rebinding
Source GCVE Database
Not known to be exploited · CVSS 8.3 High : upgrade to 1.3.1-rc soon.
Data as of 18 Nov 2026, 02:04 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 6.5 |
- Patch
- Available – fixed in 1.3.1-rc
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade typecho to 1.3.1-rc.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| typechotypecho | Affected
| Fixed in
|
GitHubtypechopkg:github/typechoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Typecho before 1.3.1-rc contains a server-side request forgery vulnerability in the XML-RPC pingback.ping method where checkSafeHost() validates a hostname's resolved IP once but the subsequent outbound request performs an independent DNS resolution, creating a TOCTOU window exploitable via DNS rebinding. An unauthenticated attacker can configure a domain to return a benign IP at validation time and an internal address (loopback, RFC1918, or cloud metadata IP) at request time, causing the server to issue blind SSRF requests to arbitrary internal hosts and ports.