WordPress Core — All known versions - Unauthenticated Blind Server Side Request Forgery
CVE-2022-3590Published · Updated Action summary
Affected: 4.1.30 – 6.1.1No patch available
What to do until a fix shipsOn this page3
Overview
- Advisory ID
- CVE-2022-3590
- Product
- WordPress wordpress
- Affected
- 4.1.30 – 6.1.1
- Fixed in
- no fix yet
- Weakness
- CWE-918 SSRF
- Required access
- No account needed
- Published
- · updated
- Credit
- Simon Scannell, Thomas Chauchefoin
- Source
- Wordfence Intelligence
- Affected4.1.30 – 6.1.1
- PatchedNo fix yet
No patched version available.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:HAttack complexity- High
PR:NPrivileges required- None
UI:NUser interaction- None
S:CScope- Changed
C:LConfidentiality- Low
I:NIntegrity- None
A:NAvailability- None
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.
Not sure which version you run? Run a passive check — it reads public files only.
Remediation & mitigations
- No known patch available. Review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance.
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
References & provenance
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Timeline
CVE published
Severity medium, CVSS 4.0
Record last updated
Sources & licenses
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.