wp-includes/class-phpass.php in WordPress before 3.7.5, 3.8.x before 3.8.5, 3.9.x before 3.9.3, and 4.x before 4.0.1 allows remote attackers to cause a denial of service (CPU consumption) via a long password that is improperly handled during hashing, a similar issue to CVE-2014-9016.
CVE-2014-9034
MEDIUMCVSS v2 · 5.05.0ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: EPSS in the top 5%, EPSS 50% or more, other public exploit code (a GitHub or vendor proof of concept, or an Exploit-DB entry not marked verified).First public exploit code on record: 2014-12-01 (Exploit-DB EDB-35413, and 1 more reference that day)EchelonGraph confidence 42%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreLOW confidence
“—” beside the score: it is equal to NVD's CVSS v2 base score.
This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — NVD rates that MEDIUM (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:L/Au:N/C:N/I:N/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 83% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.
Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
5.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- High exploitation likelihood — EPSS 83%
- Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 83%CVSS v2: 5.0Exploit: Public PoCExposed services: Not assessed
A fix is available — apply it.
- CVSS v2.0 (legacy)
- 5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
- EG Score
- 5.0MEDIUMlow confidence
- EG Risk
- 56EG Risk 56/100
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 (value × EchelonGraph’s weight)Severity50% × 45%The EG Score, 5.0 of 10.Exploitation83% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 83%
- EPSS %ILE
- 99th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 25, 2014
Last Modified
May 6, 2026
References (7)
- MITRE · CVE Programhttp://advisories.mageia.org/MGASA-2014-0493.html
- MITRE · CVE Programhttp://core.trac.wordpress.org/changeset/30467Vendor Advisory
- MITRE · CVE Programhttp://openwall.com/lists/oss-security/2014/11/25/12
- MITRE · CVE Programhttp://www.debian.org/security/2014/dsa-3085
- MITRE · CVE Programhttp://www.mandriva.com/security/advisories?name=MDVSA-2014:233
- MITRE · CVE Programhttp://www.securitytracker.com/id/1031243
- MITRE · CVE Programhttps://wordpress.org/news/2014/11/wordpress-4-0-1/Patch · Vendor Advisory
Affected Packages
(6 across 6 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| wordpress | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| wordpress | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| wordpress | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| wordpress | — |
| — |
Debian:6.0(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| wordpress | 3.0.4+dfsg-1 ... 3.6.1+dfsg-1~deb6u5 (27 versions) |
| — |
Debian:7(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| wordpress | 3.5.1+dfsg-2 ... 3.6.1+dfsg-1~deb7u4 (18 versions) |
| — |
Data Freshness Timeline
(refreshed 4× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 18 repeat rows among the latest 94 are merged into the row they repeat.
- 2026-10-12 01:20 UTCEG score recompute
- 2026-10-11 13:40 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-10-07 23:39 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-10-06 15:11 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-09-30 14:58 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-09-30 08:59 UTCEG score recompute
- 2026-09-29 15:32 UTCOSV refresh
- 2026-09-27 13:39 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-09-26 15:53 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-09-18 19:21 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-09-12 14:55 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-09-11 09:31 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-09-10 05:23 UTCOSV refresh
- 2026-09-06 13:42 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-09-05 15:23 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-09-04 13:55 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-09-02 14:07 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-08-30 19:12 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-08-28 21:34 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-08-27 14:20 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-08-26 14:41 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-08-23 04:24 UTCOSV refresh
- 2026-08-20 22:50 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-08-19 16:59 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-08-18 13:43 UTCEPSS rescoreEPSS 83% · 99th percentile
Show 51 moreShow fewer
- 2026-08-16 02:09 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-08-08 16:31 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-08-07 16:21 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-08-07 07:27 UTCOSV refresh
- 2026-08-05 19:12 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-28 15:31 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-26 14:50 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-26 13:52 UTCEG score recomputeAssessed again: 5.0 MEDIUM
- 2026-07-24 14:13 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-23 01:14 UTCEG score recompute▼ 8.60
- 2026-07-23 00:18 UTCEG score recomputeFirst assessed: 8.6 HIGH
- 2026-07-22 21:56 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-21 23:48 UTCOSV refresh
- 2026-07-21 15:21 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-20 17:03 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-15 16:54 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-15 01:56 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-13 06:08 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-09 19:05 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-07 13:42 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-04 18:56 UTCOSV refresh
- 2026-07-04 06:27 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-07-01 15:02 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-06-27 03:05 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-06-24 14:02 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-06-23 21:30 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-06-21 01:57 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-06-16 17:49 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-06-16 06:13 UTCOSV refresh
- 2026-06-14 23:14 UTCEPSS rescoreEPSS 80% · 99th percentile
- 2026-06-12 23:08 UTCEPSS rescoreEPSS 80% · 99th percentile
- 2026-06-10 22:15 UTCEPSS rescoreEPSS 80% · 99th percentile
- 2026-06-08 14:14 UTCEPSS rescoreEPSS 80% · 99th percentile
- 2026-06-07 15:22 UTCEPSS rescoreEPSS 80% · 99th percentile
- 2026-06-06 13:45 UTCEPSS rescoreEPSS 80% · 99th percentile
- 2026-06-05 22:44 UTCEPSS rescoreEPSS 80% · 99th percentile
- 2026-06-05 06:08 UTCEPSS rescoreEPSS 78% · 99th percentile
- 2026-06-04 13:09 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-06-02 20:10 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-06-01 13:49 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-05-31 00:14 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-05-29 13:41 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-05-28 14:53 UTCEG score recompute
- 2026-05-28 14:53 UTCGHSA enrichmentGHSA-wh45-5f5h-v3mq
- 2026-05-28 13:42 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-05-27 13:38 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-05-24 16:43 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-05-21 22:39 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-05-20 22:37 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-05-18 21:29 UTCEPSS rescoreEPSS 72% · 98th percentile
Publicly available exploits
(2 references)Public exploit code is referenced for this CVE (2 Exploit-DB entries). Defenders should treat patch urgency accordingly.
- Exploit-DBEDB-35413Published Dec 1, 2014
WordPress Core 4.0 - Denial of Service
Open source ↗ - Exploit-DBEDB-35414Published Dec 1, 2014
WordPress Core < 4.0.1 - Denial of Service
Open source ↗
Related CVEs(same product)
Same product
10 shownDebian:6.0:wordpress
Frequently asked(4)
What is CVE-2014-9034?
CVE-2014-9034 is a medium-severity vulnerability; its CVE record was published on November 25, 2014. wp-includes/class-phpass.php in WordPress before 3.7.5, 3.8.x before 3.8.5, 3.9.x before 3.9.3, and 4.x before 4.0.1 allows remote attackers to cause a denial of service (CPU consumption) via a long password that is improperly handled during hashing, a similar issue to CVE-2014-9016.
When was CVE-2014-9034 made public?
CVE-2014-9034 was made public on November 20, 2014: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on November 25, 2014. EchelonGraph's copy of the record carries a last-modified date of May 6, 2026; the record at its source may have been updated since.
Is CVE-2014-9034 actively exploited?
CVE-2014-9034 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2014-9034?
A fix for CVE-2014-9034 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-9034
Is Your Infrastructure Affected by CVE-2014-9034?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.