WordPress Core - All known versions - Unauthenticated Blind Server Side Request Forgery
Strategic Overview
- Status
- Unpatched
- Affected Core
- WordPress 6.1
- Affected Version
4.1.30 – 6.1.1- CVSS
- 4.0Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2022-3590
At a glance
CVE-2022-3590 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the WordPress 6.1 WordPress release line, affecting 4.1.30 – 6.1.1. It carries a CVSS score of 4.0 (reachable over the network). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed September 2022, reported by Simon Scannell.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in WordPress 6.1 4.1.30 – 6.1.1 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. No fixed build of this release line is recorded for WordPress 6.1 yet, so installs running 4.1.30 – 6.1.1 stay exposed until the vendor ships one.
Remediation
No known patch available. Review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance.
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
- 7.7CVE-2017-9066: WordPress Core < 4.7.5 Server-Side Request Forgery
CVE-2017-9066 - 7.7CVE-2014-9038: WordPress Core < 4.0.1 Server-Side Request Forgery
CVE-2014-9038 - 6.4CVE-2016-2222: WordPress Core < 4.4.2 Server-Side Request Forgery
CVE-2016-2222 - 5.8WordPress Core <= 7.0.2 Blind Server-Side Request Forgery
Other vulnerabilities in WordPress 6.1
- 9.8CVE-2026-63030: WordPress Core 6.9 - 7.0.1 Remote Code Execution
CVE-2026-63030 - 9.8CVE-2024-31211: WordPress Core 6.4.0 - 6.4.1 RCE POP Chain
CVE-2024-31211 - 9.8WordPress Core < 6.0.3 SQL Injection via WP_Date_Query
- 9.8CVE-2021-29476: WordPress Core < 5.5.3 PHP Object Injection Gadget
CVE-2021-29476 - 9.8CVE-2017-16510: WordPress Core SQL Injection
CVE-2017-16510 - 9.8CVE-2017-14723: WordPress Core < 4.8.2 SQL Injection
CVE-2017-14723 - 9.8CVE-2007-6013: WordPress Core 1.5 - 2.3.1 Authorization Bypass
CVE-2007-6013 - 9.8CVE-2007-6318: WordPress Core < 2.3.2 SQL Injection
CVE-2007-6318
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C