http/vulnerabilities/wordpress/wordpress-xmlrpc-detect.yaml

id: wordpress-xmlrpc-detect

info:
  name: WordPress XMLRPC
  author: udit_thakkur
  severity: info
  metadata:
    max-request: 1
  tags: wordpress,vuln

http:
  - method: GET
    path:
      - "{{BaseURL}}/xmlrpc.php"

    matchers:
      - type: word
        words:
          - 'XML-RPC server accepts POST requests only.'
# digest: 4a0a00473045022100ed3f0a9963221e2b460d951f50e6d7a1ae31edd7d623d3a07016b778c35ef7c602201409142afc70079a03b17b6b99ce69a22cb43fd4b30368c6f6120692cad30ce0:922c64590222798bb761d5b6d8e72950
feat: change id and some name 2025-07-21 19:07:12 +07:00			`id: wordpress-xmlrpc-detect`
Detect wordpress xmlrpc (sometimes get ssrf) Provides a way to detect the wordpress xmlrpc endpoint that can help and leads to possible ssrf sometimes. I am not sure if it is worth to add. But I have got a few good findings using this. Let me know if I'm doing it right, You guys are doing great work, Love this project. Kudos..! Trying to contribute a little. 2020-06-27 17:14:59 +05:30
			`info:`
feat: change id and some name 2025-07-21 19:07:12 +07:00			`name: WordPress XMLRPC`
Detect wordpress xmlrpc (sometimes get ssrf) Provides a way to detect the wordpress xmlrpc endpoint that can help and leads to possible ssrf sometimes. I am not sure if it is worth to add. But I have got a few good findings using this. Let me know if I'm doing it right, You guys are doing great work, Love this project. Kudos..! Trying to contribute a little. 2020-06-27 17:14:59 +05:30			`author: udit_thakkur`
uniform severity update 2020-08-04 03:22:00 +05:30			`severity: info`
Added max request counter of each template 2023-04-28 13:41:21 +05:30			`metadata:`
			`max-request: 1`
feat: Implement asset-discovery and vulnerability detection distinction 2025-10-17 14:17:02 +02:00			`tags: wordpress,vuln`
Detect wordpress xmlrpc (sometimes get ssrf) Provides a way to detect the wordpress xmlrpc endpoint that can help and leads to possible ssrf sometimes. I am not sure if it is worth to add. But I have got a few good findings using this. Let me know if I'm doing it right, You guys are doing great work, Love this project. Kudos..! Trying to contribute a little. 2020-06-27 17:14:59 +05:30
Refactoring the directory structure based on protocols (#7137) * moving http templates * updated cves.json * moved network CVEs * updated scripts * updated workflows * updated requests to http * replaced network to tcp --------- Co-authored-by: sandeep <8293321+ehsandeep@users.noreply.github.com> 2023-04-27 09:58:59 +05:30			`http:`
Detect wordpress xmlrpc (sometimes get ssrf) Provides a way to detect the wordpress xmlrpc endpoint that can help and leads to possible ssrf sometimes. I am not sure if it is worth to add. But I have got a few good findings using this. Let me know if I'm doing it right, You guys are doing great work, Love this project. Kudos..! Trying to contribute a little. 2020-06-27 17:14:59 +05:30			`- method: GET`
			`path:`
			`- "{{BaseURL}}/xmlrpc.php"`
templateman update 2023-10-14 16:57:55 +05:30
Detect wordpress xmlrpc (sometimes get ssrf) Provides a way to detect the wordpress xmlrpc endpoint that can help and leads to possible ssrf sometimes. I am not sure if it is worth to add. But I have got a few good findings using this. Let me know if I'm doing it right, You guys are doing great work, Love this project. Kudos..! Trying to contribute a little. 2020-06-27 17:14:59 +05:30			`matchers:`
moving files 2021-01-21 23:11:15 +05:30			`- type: word`
			`words:`
			`- 'XML-RPC server accepts POST requests only.'`
chore: sign templates 🤖 2025-10-26 16:17:34 +00:00			`# digest: 4a0a00473045022100ed3f0a9963221e2b460d951f50e6d7a1ae31edd7d623d3a07016b778c35ef7c602201409142afc70079a03b17b6b99ce69a22cb43fd4b30368c6f6120692cad30ce0:922c64590222798bb761d5b6d8e72950`