CVE-2019-17669

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5%CVSS: 9.8Exploit: None knownExposed: 0

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

WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because URL validation does not consider the interpretation of a name as a series of hex characters.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
51(Track)
EG Risk 51/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
Severity98% × 45%
Exploitation5% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
5%
EPSS %ILE
92%
KEV
Not listed

Published

October 17, 2019

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated Sep 13, 2026
Patch available. Sources: github_commit.
generic

[SECURITY] [DSA 4677-1] wordpress security update

https://www.debian.org/security/2020/dsa-4677
generic

[SECURITY] [DSA 4599-1] wordpress security update

https://www.debian.org/security/2020/dsa-4599
generic Patch Available

WordPress 5.2.4 Security Release – WordPress News

https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/
generic

Bugtraq: [SECURITY] [DSA 4599-1] wordpress security update

https://seclists.org/bugtraq/2020/Jan/8
generic Patch Available

[SECURITY] [DLA 1980-1] wordpress security update

https://lists.debian.org/debian-lts-announce/2019/11/msg00000.html
github_commit

commit 608d39faed63 (WordPress/WordPress)

Fix landed in WordPress/WordPress commit 608d39faed63 — awaiting tagged release

https://github.com/WordPress/WordPress/commit/608d39faed63ea212b6c6cdf9fe2bef92e2120ea

Affected Packages

(6 across 6 ecosystems)
Debian:10(1)
PackageVulnerable rangeFixed inDependents
wordpress5.0.4+dfsg1-15.0.4+dfsg1-1+deb10u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
wordpress—5.2.4+dfsg1-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
wordpress—5.2.4+dfsg1-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
wordpress—5.2.4+dfsg1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
wordpress—5.2.4+dfsg1-1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
wordpress4.1+dfsg-1 ... 4.1.27+dfsg-0+deb8u1 (23 versions)4.1.28+dfsg-0+deb8u1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 24× 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.

Showing the most recent 100 of 139 total refreshes for this CVE.

  1. 2026-09-18 19:22 UTCEPSS rescore
  2. 2026-09-17 19:22 UTCEPSS rescore
  3. 2026-09-16 14:04 UTCEPSS rescore
  4. 2026-09-15 03:05 UTCEPSS rescore
  5. 2026-09-12 14:56 UTCEPSS rescore
  6. 2026-09-11 14:48 UTCEPSS rescore
  7. 2026-09-11 09:32 UTCEPSS rescore
  8. 2026-09-08 02:14 UTCOSV refresh
  9. 2026-09-07 15:57 UTCEPSS rescore
  10. 2026-09-06 13:44 UTCEPSS rescore
  11. 2026-09-05 15:24 UTCEPSS rescore
  12. 2026-09-04 13:56 UTCEPSS rescore
  13. 2026-09-02 14:07 UTCEPSS rescore
  14. 2026-09-01 03:32 UTCEPSS rescore
  15. 2026-08-30 19:13 UTCEPSS rescore
  16. 2026-08-30 01:18 UTCEPSS rescore
  17. 2026-08-28 21:36 UTCEPSS rescore
  18. 2026-08-27 14:21 UTCEPSS rescore
  19. 2026-08-26 14:42 UTCEPSS rescore
  20. 2026-08-25 13:45 UTCEPSS rescore
  21. 2026-08-24 14:11 UTCEPSS rescore
  22. 2026-08-21 23:45 UTCEPSS rescore
  23. 2026-08-21 12:44 UTCOSV refresh
  24. 2026-08-20 22:51 UTCEPSS rescore
  25. 2026-08-19 17:00 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:44 UTCEPSS rescore
  2. 2026-08-17 13:43 UTCEPSS rescore
  3. 2026-08-16 14:52 UTCEPSS rescore
  4. 2026-08-16 02:10 UTCEPSS rescore
  5. 2026-08-15 01:26 UTCEPSS rescore
  6. 2026-08-12 13:47 UTCEPSS rescore
  7. 2026-08-09 13:43 UTCEPSS rescore
  8. 2026-08-08 16:33 UTCEPSS rescore
  9. 2026-08-07 16:23 UTCEPSS rescore
  10. 2026-08-06 13:43 UTCEPSS rescore
  11. 2026-08-05 23:51 UTCOSV refresh
  12. 2026-08-05 19:13 UTCEPSS rescore
  13. 2026-08-04 15:05 UTCEPSS rescore
  14. 2026-08-02 02:23 UTCEPSS rescore
  15. 2026-08-01 04:12 UTCEPSS rescore
  16. 2026-07-30 16:24 UTCEPSS rescore
  17. 2026-07-30 01:27 UTCEPSS rescore
  18. 2026-07-28 15:32 UTCEPSS rescore
  19. 2026-07-25 14:14 UTCEPSS rescore
  20. 2026-07-24 14:14 UTCEPSS rescore
  21. 2026-07-24 14:14 UTCEPSS rescore
  22. 2026-07-23 14:15 UTCEPSS rescore
  23. 2026-07-23 01:42 UTCEG score recompute
  24. 2026-07-22 22:22 UTCEG score recompute
  25. 2026-07-22 14:05 UTCEPSS rescore
  26. 2026-07-21 15:22 UTCEPSS rescore
  27. 2026-07-21 15:22 UTCEPSS rescore
  28. 2026-07-20 17:04 UTCEPSS rescore
  29. 2026-07-20 17:04 UTCEPSS rescore
  30. 2026-07-20 03:40 UTCOSV refresh
  31. 2026-07-19 14:28 UTCEPSS rescore
  32. 2026-07-19 14:28 UTCEPSS rescore
  33. 2026-07-19 02:26 UTCEPSS rescore
  34. 2026-07-19 02:26 UTCEPSS rescore
  35. 2026-07-18 10:01 UTCEPSS rescore
  36. 2026-07-16 16:59 UTCEPSS rescore
  37. 2026-07-16 16:59 UTCEPSS rescore
  38. 2026-07-15 16:55 UTCEPSS rescore
  39. 2026-07-15 16:55 UTCEPSS rescore
  40. 2026-07-13 22:27 UTCEPSS rescore
  41. 2026-07-12 05:43 UTCEPSS rescore
  42. 2026-07-12 05:43 UTCEPSS rescore
  43. 2026-07-11 08:24 UTCEPSS rescore
  44. 2026-07-11 08:24 UTCEPSS rescore
  45. 2026-07-09 19:06 UTCEPSS rescore
  46. 2026-07-08 15:11 UTCEPSS rescore
  47. 2026-07-07 13:43 UTCEPSS rescore
  48. 2026-07-06 16:25 UTCEPSS rescore
  49. 2026-07-06 16:25 UTCEPSS rescore
  50. 2026-07-06 02:20 UTCEPSS rescore
  51. 2026-07-05 02:27 UTCEPSS rescore
  52. 2026-07-04 06:28 UTCEPSS rescore
  53. 2026-07-02 18:06 UTCOSV refresh
  54. 2026-07-01 15:03 UTCEPSS rescore
  55. 2026-07-01 15:03 UTCEPSS rescore
  56. 2026-06-30 23:20 UTCEPSS rescore
  57. 2026-06-29 14:03 UTCEPSS rescore
  58. 2026-06-28 14:04 UTCEPSS rescore
  59. 2026-06-28 04:54 UTCEPSS rescore
  60. 2026-06-28 04:54 UTCEPSS rescore
  61. 2026-06-27 03:06 UTCEPSS rescore
  62. 2026-06-25 13:47 UTCEPSS rescore
  63. 2026-06-25 13:47 UTCEPSS rescore
  64. 2026-06-24 14:03 UTCEPSS rescore
  65. 2026-06-24 14:03 UTCEPSS rescore
  66. 2026-06-23 21:31 UTCEPSS rescore
  67. 2026-06-23 21:30 UTCEPSS rescore
  68. 2026-06-22 14:23 UTCEPSS rescore
  69. 2026-06-21 14:54 UTCEPSS rescore
  70. 2026-06-21 14:54 UTCEPSS rescore
  71. 2026-06-21 01:57 UTCEPSS rescore
  72. 2026-06-21 01:57 UTCEPSS rescore
  73. 2026-06-19 19:23 UTCEPSS rescore
  74. 2026-06-19 19:23 UTCEPSS rescore
  75. 2026-06-18 17:50 UTCEPSS rescore

Frequently asked(5)

What is CVE-2019-17669?
CVE-2019-17669 is a critical vulnerability published on October 17, 2019. WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because URL validation does not consider the interpretation of a name as a series of hex characters.
When was CVE-2019-17669 disclosed?
CVE-2019-17669 was first published in the National Vulnerability Database on October 17, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-17669 actively exploited?
CVE-2019-17669 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5% probability of exploitation in the next 30 days, which ranks it in the top 7.8% of all scored CVEs.
What is the CVSS score of CVE-2019-17669?
CVE-2019-17669 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-17669?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-17669, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-17669

Explore →

Is Your Infrastructure Affected by CVE-2019-17669?

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

Start Free Scan →Browse All CVEs