How severe is CVE-2022-3590?

CVE-2022-3590 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-3590?

Affected package information for CVE-2022-3590 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2022-3590?

No fixed version has been published for CVE-2022-3590 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2022-3590 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2022-3590, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-3590?

CVE-2022-3590 has an EPSS (Exploit Prediction Scoring System) score of 90.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is there exploit tooling available for CVE-2022-3590?

A Nuclei detection template exists for CVE-2022-3590, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2022-3590 published, and has it been updated?

CVE-2022-3590 was published on December 14, 2022 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2022-3590

MEDIUM

Also known asBIT-wordpress-2022-3590BIT-wordpress-multisite-2022-3590

Published

Dec 14, 2022

Updated

Apr 10, 2026

Affected

0 pkgs

Patched

None yet

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

90.3%probability of exploitation in next 30 days

Very High Risk100th percentile+0.31%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

WordPress is affected by an unauthenticated blind SSRF in the pingback f…

blog.sonarsource.comNVDDec 2022

WordPress is affected by an unauthenticated blind SSRF in the pingback f…

github.comGithubJun 2023

WordPress is affected by an unauthenticated blind SSRF in the pingback f…

media.defense.govAPISep 2024

WordPress is affected by an unauthenticated blind SSRF in the pingback f…

github.comGithubJun 2023

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-3590 in your stack?

O3 detects CVE-2022-3590 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works