CVE-2022-3590 json
WP <= 6.1.1 - Unauthenticated Blind SSRF via DNS Rebinding
published 2022-12-14 3 y ago modified 2026-09-08 2 mo ago also BIT-wordpress-2022-3590 , BIT-wordpress-multisite-2022-3590 , EUVD-2022-42954
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.4%
- EPSS 3.4% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
Patch / fix
- bitnami wordpress 4.1.1, 6.1.2
- bitnami wordpress-multisite 4.1.1, 6.1.2
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-3590 updated cvss 9.8
wordpress: WordPress is affected by an unauthenticated blind SSRF in the pingback feature.
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
3.43% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template WordPress <= 6.2 - Server Side Request Forgery nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/c8814e6e-78b3-4f63-a1d3-6906a84c1f11 referenced PoC, tagged "exploit" by a source, unverified
- blog.sonarsource.com https://blog.sonarsource.com/wordpress-core-unauthenticated-blind-ssrf/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | wordpress | >=4.1.0, <4.1.1 >=4.2.0, <6.1.2 |
4.1.1 6.1.2 |
| bitnami | wordpress-multisite | >=4.1.0, <4.1.1 >=4.2.0, <6.1.2 |
4.1.1 6.1.2 |
Affected products
- WordPress WordPress
Classification
- Weakness
-
- CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
- Technology feeds
References
-
wpscan.com
/vulnerability/c8814e6e-78b3-4f63-a1d3-6906a84c1f11
exploit, vdb-entry, technical-description, third-party-advisory, advisory
-
blog.sonarsource.com
/wordpress-core-unauthenticated-blind-ssrf/
exploit, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-3590
web
Sources
- CVE List CVE-2022-3590
- NVD CVE-2022-3590
- OSV BIT-wordpress-2022-3590
- OSV BIT-wordpress-multisite-2022-3590
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.