CVE-2026-22201

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-03-13. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

wpDiscuz before 7.6.47 contains an IP spoofing vulnerability in the getIP() function that allows attackers to bypass IP-based rate limiting and ban enforcement by trusting untrusted HTTP headers. Attackers can set HTTP_CLIENT_IP or HTTP_X_FORWARDED_FOR headers to spoof their IP address and circumvent security controls.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

March 13, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
No patch confirmed yet.
generic

wpDiscuz before 7.6.47 - IP Address Spoofing in getIP() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/wpdiscuz-before-ip-address-spoofing-in-getip
generic

Comments – wpDiscuz – WordPress plugin | WordPress.org

https://wordpress.org/plugins/wpdiscuz/#developers
generic

Comments – wpDiscuz – WordPress plugin | WordPress.org

https://wordpress.org/plugins/wpdiscuz/

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-12 15:01 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:48 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 41 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 11:40 UTCEG score recompute
  4. 2026-08-16 11:40 UTCGHSA enrichment
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 07:41 UTCEG score recompute
  8. 2026-08-14 07:41 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-12 22:40 UTCEG score recompute
  11. 2026-08-12 22:40 UTCGHSA enrichment
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-11 13:42 UTCEPSS rescore
  14. 2026-08-11 07:15 UTCEG score recompute
  15. 2026-08-11 07:14 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 07:18 UTCEG score recompute
  18. 2026-08-10 07:18 UTCGHSA enrichment
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-09 07:21 UTCEG score recompute
  21. 2026-08-09 07:21 UTCGHSA enrichment
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-07 18:01 UTCEG score recompute
  24. 2026-08-07 18:01 UTCGHSA enrichment
  25. 2026-08-06 13:46 UTCEPSS rescore
  26. 2026-08-06 01:54 UTCEG score recompute
  27. 2026-08-06 01:54 UTCGHSA enrichment
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-04 15:10 UTCEPSS rescore
  30. 2026-08-04 10:38 UTCEPSS rescore
  31. 2026-08-04 01:10 UTCEG score recompute
  32. 2026-08-04 01:10 UTCGHSA enrichment
  33. 2026-08-03 10:35 UTCEPSS rescore
  34. 2026-08-02 17:18 UTCEG score recompute
  35. 2026-08-02 17:18 UTCGHSA enrichment
  36. 2026-08-02 02:26 UTCEPSS rescore
  37. 2026-08-01 04:15 UTCEPSS rescore
  38. 2026-07-30 01:30 UTCEPSS rescore
  39. 2026-07-27 14:13 UTCEPSS rescore
  40. 2026-07-27 13:38 UTCEG score recompute
  41. 2026-07-27 13:38 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-22201?
CVE-2026-22201 is a medium vulnerability published on March 13, 2026. wpDiscuz before 7.6.47 contains an IP spoofing vulnerability in the getIP() function that allows attackers to bypass IP-based rate limiting and ban enforcement by trusting untrusted HTTP headers. Attackers can set HTTPCLIENTIP or HTTPXFORWARDED_FOR headers to spoof their IP address and circumvent…
When was CVE-2026-22201 disclosed?
CVE-2026-22201 was first published in the National Vulnerability Database on March 13, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-22201 actively exploited?
CVE-2026-22201 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.2% of all scored CVEs.
What is the CVSS score of CVE-2026-22201?
CVE-2026-22201 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-22201?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22201, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-22201

Explore →

Is Your Infrastructure Affected by CVE-2026-22201?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs