CVE-2010-1870

MEDIUMCVSS v2 · 5.05.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:N/I:P/A:N. 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 91.1% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
5.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 91%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 91%CVSS v2: 5.0Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

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

The OGNL extensive expression evaluation capability in XWork in Struts 2.0.0 through 2.1.8.1, as used in Atlassian Fisheye, Crucible, and possibly other products, uses a permissive whitelist, which allows remote attackers to modify server-side context objects and bypass the "#" protection mechanism in ParameterInterceptors via the (1) #context, (2) #_memberAccess, (3) #root, (4) #this, (5) #_typeResolver, (6) #_classResolver, (7) #_traceEvaluations, (8) #_lastEvaluation, (9) #_keepLastEvaluation, and possibly other OGNL context variables, a different vulnerability than CVE-2008-6504.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0(low)
EG Risk
63(Track)
EG Risk 63/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
Severity50% × 45%
Exploitation91% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
91%
EPSS %ILE
100%
KEV
Not listed

Published

August 17, 2010

Last Modified

April 29, 2026

References (24)

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.struts:struts2-core2.0.11 ... 2.1.8.1 (13 versions)2.2.1—

Data Freshness Timeline

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

  1. 2026-07-26 13:40 UTCEG score recompute▲ 5.00
  2. 2026-07-23 00:42 UTCEG score recompute
  3. 2026-07-23 00:38 UTCEG score recompute▼ 9.00
  4. 2026-07-23 00:06 UTCEG score recompute
  5. 2026-07-22 21:45 UTCEG score recompute
  6. 2026-07-22 14:03 UTCEPSS rescore
  7. 2026-07-22 14:03 UTCEPSS rescore
  8. 2026-07-15 16:54 UTCEPSS rescore
  9. 2026-07-15 16:54 UTCEPSS rescore
  10. 2026-06-28 04:52 UTCEPSS rescore
  11. 2026-06-28 04:52 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-23 21:29 UTCEPSS rescore
  14. 2026-06-16 17:49 UTCEPSS rescore
  15. 2026-06-15 17:44 UTCEPSS rescore
  16. 2026-06-13 22:57 UTCEPSS rescore
  17. 2026-06-13 22:57 UTCEPSS rescore
  18. 2026-06-13 22:57 UTCEPSS rescore
  19. 2026-06-12 23:08 UTCEPSS rescore
  20. 2026-06-12 23:08 UTCEPSS rescore
  21. 2026-06-05 22:44 UTCEPSS rescore
  22. 2026-06-05 22:44 UTCEPSS rescore
  23. 2026-05-31 22:28 UTCEPSS rescore
  24. 2026-05-31 22:28 UTCEPSS rescore
  25. 2026-05-29 13:40 UTCEPSS rescore
Show 11 more
  1. 2026-05-29 10:38 UTCEG score recompute
  2. 2026-05-27 13:38 UTCEPSS rescore
  3. 2026-05-27 13:38 UTCEPSS rescore
  4. 2026-05-22 21:15 UTCEPSS rescore
  5. 2026-05-22 21:15 UTCEPSS rescore
  6. 2026-05-22 21:15 UTCEPSS rescore
  7. 2026-05-20 22:37 UTCEPSS rescore
  8. 2026-05-20 22:37 UTCEPSS rescore
  9. 2026-05-20 22:37 UTCEPSS rescore
  10. 2026-05-18 21:29 UTCEPSS rescore
  11. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(4 references)

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

  • Exploit-DBEDB-17691✓ verified
    First seen Aug 19, 2011

    Apache Struts < 2.2.0 - Remote Command Execution (Metasploit)

    Open source ↗
  • Exploit-DBEDB-14360
    First seen Jul 14, 2010

    Struts2/XWork < 2.2.0 - Remote Command Execution

    Open source ↗
  • Metasploitexploit/multi/http/struts_code_exec✓ verified
    First seen Jul 13, 2010

    Apache Struts Remote Command Execution

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

    ListSERV Maestro <= 9.0-8 RCE

    Open source ↗

Frequently asked(4)

What is CVE-2010-1870?
CVE-2010-1870 is a medium vulnerability published on August 17, 2010. The OGNL extensive expression evaluation capability in XWork in Struts 2.0.0 through 2.1.8.1, as used in Atlassian Fisheye, Crucible, and possibly other products, uses a permissive whitelist, which allows remote attackers to modify server-side context objects and bypass the "#" protection mechanism…
When was CVE-2010-1870 disclosed?
CVE-2010-1870 was first published in the National Vulnerability Database on August 17, 2010, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2010-1870 actively exploited?
CVE-2010-1870 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
How do I remediate CVE-2010-1870?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2010-1870, 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-2010-1870

Explore →

Is Your Infrastructure Affected by CVE-2010-1870?

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

Start Free Scan →Browse All CVEs