WordPress Core - All known versions - Unauthenticated Blind Server Side Request Forgery

Server-Side Request Forgery (SSRF)
CVE CVE-2022-3590
CVSS 4.0 (Medium)
Publicly Published September 6, 2022
Last Updated January 22, 2024
Researchers Simon Scannell
Thomas Chauchefoin


WordPress Core, in all known versions is vulnerable to blind Server-Side Request Forgery in its pingback feature. This is due to a Time-of-Check-Time-of-Use (TOC-TOU) race condition between validation checks and HTTP requests that makes it possible for URLs to be validated and then changed before being used by the software. This makes it possible for an attacker to change the domain in a pingback request to point to a different address than the one validated before, thus exposing hosts that should not be reachable on a server. The original researcher couldn't identify any ways to exploit this to take over vulnerable sites without other vulnerable services on the site meaning this would be difficult to exploit. The issue was first reported in 2017 and it's recommendd to block xmlrpc.php at the web server level, if not in use to prevent this from being exploited.



1 affected software package

Software Type Core
Patched? No
Remediation No known patch available. Review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance.
Affected Version
  • All Versions

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.