CVE-2014-0114

HIGHCVSS v2 · 7.57.5
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 7.5 — NVD rates that HIGH (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:P/I:P/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 99% 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
Trending — 5 sources updated this weekWeaponized

Also known asEUVD-2020-0504 (ENISA EUVD) · GHSA-p66x-2cv9-qq3v (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
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 99%
  • Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 99%CVSS v2: 7.5Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in Apache Struts 1.x through 1.3.10 and in other products requiring commons-beanutils through 1.9.2, does not suppress the class property, which allows remote attackers to "manipulate" the ClassLoader and execute arbitrary code via the class parameter, as demonstrated by the passing of this parameter to the getClass method of the ActionForm object in Struts 1.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5HIGHlow confidence
EG Risk
88
EG Risk 88/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation99% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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
99%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v2.0 · CVSS v2.0AV:N/AC:L/Au:N/C:P/I:P/A:P
EG Likelihood
99% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

April 30, 2014

Last Modified

October 14, 2026

References (119)

15 of 119 shown · show the other 104

Vendor Advisories for CVE-2014-0114(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibcommons-beanutils-java-doc (1.9.2-3ubuntu0.1~esm2) @ xenial2026-10-30ubuntu
ubuntulibcommons-beanutils-java-doc (1.9.2-3ubuntu0.1~esm1) @ xenial2026-10-30ubuntu
redhatpatch2019-10-10redhat
redhatpatch2018-09-11redhat
redhatpatch2014-05-15redhat
redhatstruts-0:1.3.10-6.ep5.el62014-05-14redhat
redhatpatch2014-05-14redhat
redhatpatch2014-05-14redhat
redhatstruts-0:1.2.9-4jpp.8.el5_102014-05-07redhat
mavencommons-beanutils:commons-beanutils @ 1.9.4 (fixes >= 1.8.0, < 1.9.4)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
commons-beanutils—
  • every version up to 1.9.2-1: fixed in 1.9.2-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
commons-beanutils—
  • every version up to 1.9.2-1: fixed in 1.9.2-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
commons-beanutils—
  • every version up to 1.9.2-1: fixed in 1.9.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
commons-beanutils—
  • every version up to 1.9.2-1: fixed in 1.9.2-1
—
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
libstruts1.2-java1.2.9-4
  • every version up to 1.2.9-4+deb6u1: fixed in 1.2.9-4+deb6u1
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
libstruts1.2-java1.2.9-5
  • every version up to 1.2.9-5+deb7u1: fixed in 1.2.9-5+deb7u1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
commons-beanutils:commons-beanutils1.8.0 ... 1.9.3 (8 versions)
  • 1.8.0 up to 1.9.4: fixed in 1.9.4
—

Weakness Classification(1)

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

Additional Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 6× in last 7d / 21× 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. 17 repeat rows among the latest 86 are merged into the row they repeat.

  1. 2026-11-01 08:50 UTCGHSA enrichmentGHSA-p66x-2cv9-qq3v · GitHub severity HIGH
  2. 2026-11-01 08:50 UTCEG score recompute
  3. 2026-10-31 16:26 UTCEPSS rescoreEPSS 99% · 99th percentile
  4. 2026-10-30 03:09 UTCEG score recompute
  5. 2026-10-30 03:09 UTCVendor advisory
  6. 2026-10-29 19:55 UTCOSV refresh
  7. 2026-10-25 20:05 UTCEG score recompute
  8. 2026-10-25 16:26 UTCEPSS rescoreEPSS 99% · 99th percentile
  9. 2026-10-22 10:59 UTCEG score recompute
  10. 2026-10-22 10:59 UTCVendor advisory
  11. 2026-10-19 16:26 UTCEPSS rescoreEPSS 99% · 99th percentile
  12. 2026-10-18 11:15 UTCEG score recompute
  13. 2026-10-14 18:46 UTCEG score recompute
  14. 2026-10-14 18:46 UTCVendor advisory
  15. 2026-10-14 17:25 UTCNVD update
  16. 2026-10-14 16:29 UTCMITRE cvelistV5
  17. 2026-10-12 21:21 UTCEG score recompute
  18. 2026-10-12 01:28 UTCEG score recompute
  19. 2026-10-11 13:39 UTCEPSS rescoreEPSS 99% · 99th percentile
  20. 2026-10-10 19:54 UTCEPSS rescoreEPSS 99% · 99th percentile
  21. 2026-10-08 16:34 UTCEPSS rescoreEPSS 99% · 99th percentile
  22. 2026-10-01 04:40 UTCOSV refresh
  23. 2026-09-30 00:18 UTCEG score recompute
  24. 2026-09-21 20:25 UTCEPSS rescoreEPSS 99% · 99th percentile
  25. 2026-09-12 07:10 UTCOSV refresh
Show 44 more
  1. 2026-08-30 19:12 UTCEPSS rescoreEPSS 99% · 99th percentile
  2. 2026-08-26 14:41 UTCEPSS rescoreEPSS 99% · 99th percentile
  3. 2026-08-24 12:30 UTCOSV refresh
  4. 2026-08-18 13:43 UTCEPSS rescoreEPSS 96% · 99th percentile
  5. 2026-08-08 08:19 UTCOSV refresh
  6. 2026-07-26 13:49 UTCEG score recomputeAssessed again: 7.5 HIGH
  7. 2026-07-23 01:19 UTCVendor advisory
  8. 2026-07-23 01:17 UTCVendor advisory
  9. 2026-07-23 01:16 UTCVendor advisory
  10. 2026-07-23 01:14 UTCVendor advisory
  11. 2026-07-23 01:12 UTCVendor advisory
  12. 2026-07-23 01:11 UTCEG score recompute▼ 9.00
  13. 2026-07-23 00:15 UTCEG score recompute
  14. 2026-07-22 21:53 UTCEG score recompute
  15. 2026-07-22 14:04 UTCEPSS rescoreEPSS 96% · 99th percentile
  16. 2026-07-22 06:18 UTCOSV refresh
  17. 2026-07-13 22:26 UTCEPSS rescoreEPSS 96% · 99th percentile
  18. 2026-07-13 06:08 UTCEPSS rescoreEPSS 96% · 99th percentile
  19. 2026-07-05 00:56 UTCOSV refresh
  20. 2026-07-01 15:02 UTCEPSS rescoreEPSS 96% · 99th percentile
  21. 2026-06-30 23:19 UTCEPSS rescoreEPSS 96% · 99th percentile
  22. 2026-06-24 14:02 UTCEPSS rescoreEPSS 96% · 99th percentile
  23. 2026-06-23 21:30 UTCEPSS rescoreEPSS 96% · 99th percentile
  24. 2026-06-22 14:22 UTCEPSS rescoreEPSS 96% · 99th percentile
  25. 2026-06-21 01:57 UTCEPSS rescoreEPSS 96% · 99th percentile
  26. 2026-06-16 12:39 UTCOSV refresh
  27. 2026-06-15 17:44 UTCEPSS rescoreEPSS 96% · 99th percentile
  28. 2026-06-12 23:08 UTCEPSS rescoreEPSS 92% · 99th percentile
  29. 2026-06-10 22:15 UTCEPSS rescoreEPSS 92% · 99th percentile
  30. 2026-06-07 15:22 UTCEPSS rescoreEPSS 92% · 99th percentile
  31. 2026-06-05 22:44 UTCEPSS rescoreEPSS 92% · 99th percentile
  32. 2026-06-04 13:09 UTCEPSS rescoreEPSS 92% · 99th percentile
  33. 2026-06-02 20:10 UTCEPSS rescoreEPSS 92% · 99th percentile
  34. 2026-05-31 00:14 UTCEPSS rescoreEPSS 92% · 99th percentile
  35. 2026-05-28 19:12 UTCEG score recompute
  36. 2026-05-28 19:12 UTCVendor advisory
  37. 2026-05-28 13:42 UTCEPSS rescoreEPSS 92% · 99th percentile
  38. 2026-05-27 13:38 UTCEPSS rescoreEPSS 92% · 99th percentile
  39. 2026-05-26 07:16 UTCEPSS rescoreEPSS 92% · 99th percentile
  40. 2026-05-26 02:46 UTCOSV refresh
  41. 2026-05-22 21:15 UTCEPSS rescoreEPSS 92% · 99th percentile
  42. 2026-05-20 22:37 UTCEPSS rescoreEPSS 92% · 99th percentile
  43. 2026-05-20 11:21 UTCEPSS rescoreEPSS 92% · 99th percentile
  44. 2026-05-18 21:29 UTCEPSS rescoreEPSS 92% · 99th percentile

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 2 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-41690✓ verified
    Published Mar 23, 2017

    Apache Struts < 1.3.10 / < 2.3.16.2 - ClassLoader Manipulation Remote Code Execution (Metasploit)

    Open source ↗
  • Metasploitexploit/multi/http/struts_code_exec_classloader✓ verified
    Published May 1, 2014

    Apache Struts ClassLoader Manipulation Remote Code Execution

    Open source ↗
  • GitHub PoCaenlr/strutt-cve-2014-0114
    Published May 27, 2019
    Open source ↗
  • GitHub PoCrgielen/struts1filter
    Published May 22, 2014

    A request parameter filter solution for Struts 1 CVE-2014-0114 based on the work of Alvaro Munoz and the HP Fortify team

    Open source ↗

Frequently asked(4)

What is CVE-2014-0114?
CVE-2014-0114 is a high-severity vulnerability; its CVE record was published on April 30, 2014. Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in Apache Struts 1.x through 1.3.10 and in other products requiring commons-beanutils through 1.9.2, does not suppress the class property, which allows remote attackers to "manipulate" the ClassLoader and execute arbitrary…
When was CVE-2014-0114 made public?
CVE-2014-0114 was made public on April 29, 2014: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on April 30, 2014. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2014-0114 actively exploited?
CVE-2014-0114 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 99% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2014-0114?
A fix for CVE-2014-0114 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2014-0114 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-0114

Explore →

Is Your Infrastructure Affected by CVE-2014-0114?

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