CVE-2022-3590Public exploitNetwork attack vector

Blind SSRF via pingback DNS rebinding

Published Dec 14, 2022 · Updated Apr 21, 2025

Blind SSRF in the pingback feature in WordPress 4.1.30 through 6.1.1 allows remote attackers to reach internal hosts. The pingback.ping XML-RPC method validates pagelinkedfrom by resolving its hostname, but the HTTP transport resolves it again, allowing DNS rebinding between check and use. Pingbacks are enabled by default and require no authentication; the blind response limits direct disclosure, but the server can probe otherwise blocked internal services.

CVSS severity5.9
Medium
EPSS probability3.15%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Blind SSRF in the pingback feature in WordPress 4.1.30 through 6.1.1 allows remote attackers to reach internal hosts. The pingback.ping XML-RPC method validates pagelinkedfrom by resolving its hostname, but the HTTP transport resolves it again, allowing DNS rebinding between check and use. Pingbacks are enabled by default and require no authentication; the blind response limits direct disclosure, but the server can probe otherwise blocked internal services.

The record

CVE
CVE-2022-3590
Published
Dec 14, 2022
Updated
Apr 21, 2025
Vendor
WordPress.org
Product
WordPress
Classifications
CWE-367, CWE-918, T1046, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 14, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 21, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.1.30 <=6.1.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

WordPress.org · WordPressversion=4.1.30 <=6.1.1

Published CVSS scores

5.9NVDCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
CWE-918Server-Side Request Forgery (SSRF)
T1046Network Service Discovery
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo