CVE-2017-8295

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2022-05-17. NVD baseline CVSS 5.9; sources differ by 0.0.

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

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

WordPress through 4.7.4 relies on the Host HTTP header for a password-reset e-mail message, which makes it easier for remote attackers to reset arbitrary passwords by making a crafted wp-login.php?action=lostpassword request and then arranging for this message to bounce or be resent, leading to transmission of the reset key to a mailbox on an attacker-controlled SMTP server. This is related to problematic use of the SERVER_NAME variable in wp-includes/pluggable.php in conjunction with the PHP mail function. Exploitation is not achievable in all cases because it requires at least one of the following: (1) the attacker can prevent the victim from receiving any e-mail messages for an extended period of time (such as 5 days), (2) the victim's e-mail system sends an autoresponse containing the original message, or (3) the victim manually composes a reply containing the original message.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
47(Track)
EG Risk 47/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
Severity59% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
27%
EPSS %ILE
98%
KEV
Not listed

Published

May 4, 2017

Last Modified

June 17, 2026

References (12)

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
wordpress—4.7.5+dfsg-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
wordpress—4.7.5+dfsg-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
wordpress—4.7.5+dfsg-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
wordpress—4.7.5+dfsg-2—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
wordpress3.5.1+dfsg-2 ... 3.6.1+dfsg-1~deb7u9 (27 versions)3.6.1+dfsg-1~deb7u15—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
wordpress4.1+dfsg-1 ... 4.1+dfsg-1+deb8u9 (14 versions)4.1+dfsg-1+deb8u14—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 21× 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 126 total refreshes for this CVE.

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

Publicly available exploits

(3 references)

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

  • GitHub PoCcyberheartmi9/CVE-2017-8295
    First seen May 6, 2017
    Open source ↗
  • GitHub PoCalash3al/wp-allowed-hosts
    First seen May 5, 2017

    a plugin that protects your wp site from the CVE-2017-8295 vulnerability

    Open source ↗
  • Exploit-DBEDB-41963
    First seen May 3, 2017

    WordPress Core < 4.7.4 - Unauthorized Password Reset

    Open source ↗

Frequently asked(5)

What is CVE-2017-8295?
CVE-2017-8295 is a medium vulnerability published on May 4, 2017. WordPress through 4.7.4 relies on the Host HTTP header for a password-reset e-mail message, which makes it easier for remote attackers to reset arbitrary passwords by making a crafted wp-login.php?action=lostpassword request and then arranging for this message to bounce or be resent, leading to…
When was CVE-2017-8295 disclosed?
CVE-2017-8295 was first published in the National Vulnerability Database on May 4, 2017, 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-2017-8295 actively exploited?
CVE-2017-8295 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27% probability of exploitation in the next 30 days, which ranks it in the top 2.1% of all scored CVEs.
What is the CVSS score of CVE-2017-8295?
CVE-2017-8295 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2017-8295?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-8295, 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-2017-8295

Explore →

Is Your Infrastructure Affected by CVE-2017-8295?

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

Start Free Scan →Browse All CVEs