CVE-2019-17671

MEDIUMNVD 5.35.7▲
EchelonGraph scoreHIGH confidence

Score elevated to 5.7 because EPSS predicts 36% probability of exploitation within the next 30 days (top 1.7% of all CVEs). NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 37%CVSS: 5.3Exploit: Elevated riskExposed: 0

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

In WordPress before 5.2.4, unauthenticated viewing of certain content is possible because the static query property is mishandled.

CVSS v3
5.3
EG Score
5.7(high)
EG Risk
46(Track)
EG Risk 46/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
Severity57% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
37%
EPSS %ILE
98%
KEV
Not listed

Published

October 17, 2019

Last Modified

November 21, 2024

References (18)

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 9× in last 7d / 26× 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 105 total refreshes for this CVE.

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

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCrhbb/CVE-2019-17671
    First seen Apr 3, 2020
    Open source ↗
  • Exploit-DBEDB-47690
    First seen Oct 14, 2019

    WordPress Core < 5.2.3 - Viewing Unauthenticated/Password/Private Posts

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-17671.yaml
    First seen Jan 1, 2019

    WordPress <= 5.2.4 - Unauthenticated View Private/Draft Posts

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-17671?
CVE-2019-17671 is a medium vulnerability published on October 17, 2019. In WordPress before 5.2.4, unauthenticated viewing of certain content is possible because the static query property is mishandled.
When was CVE-2019-17671 disclosed?
CVE-2019-17671 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-17671 actively exploited?
CVE-2019-17671 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37% probability of exploitation in the next 30 days, which ranks it in the top 1.6% of all scored CVEs.
What is the CVSS score of CVE-2019-17671?
CVE-2019-17671 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.7.
How do I remediate CVE-2019-17671?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-17671, 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-17671

Explore →

Is Your Infrastructure Affected by CVE-2019-17671?

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

Start Free Scan →Browse All CVEs