CVE-2022-3590: WP <= 6.1.1 - Unauthenticated Blind SSRF via DNS Rebinding
Published Dec 14, 2022
·Updated
WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and the HTTP request, attackers can reach internal hosts that are explicitly forbidden.
Affected Software
6 affected components
WordPress WordPress>=4.2<=6.1.1
WordPress WordPress=4.1
debian/wordpress*
debian/wordpress*
debian/wordpress*
debian/wordpress<=6.1.9+dfsg1-0+deb12u1, <=6.8.7+dfsg1-0+deb13u1, <=6.8.12+dfsg1-0+deb13u1, <=7.1.4+dfsg1-1
Event History
Dec 14, 2022
CVE Published
via MITRE·08:33 AM
Data Sourced
via MITRE·08:33 AM
DescriptionWeakness
Data Sourced
via OSV·09:15 AM
DescriptionSeverityAffected Software
Jun 12, 2023
Exploit Published
via GitHub·01:06 PM
Frequently Asked Questions
1
What is the vulnerability ID of this WordPress vulnerability?
The vulnerability ID of this WordPress vulnerability is CVE-2022-3590.
2
What is the severity rating of CVE-2022-3590?
The severity rating of CVE-2022-3590 is medium (5.9).
3
How does the vulnerability in the pingback feature of WordPress affect the system?
The vulnerability allows for an unauthenticated blind server-side request forgery (SSRF) attack, potentially exposing internal hosts that are explicitly forbidden.
4
Which versions of WordPress are affected by this vulnerability?
WordPress versions 4.1 to 6.1.1 are affected by this vulnerability.
5
How can I fix the CVE-2022-3590 vulnerability in my WordPress installation?
To fix the vulnerability, update your WordPress installation to a version that has been patched to address CVE-2022-3590.