How severe is CVE-2010-1870?

No CVSS score has been assigned to CVE-2010-1870 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2010-1870?

CVE-2010-1870 affects the following packages: org.apache.struts:struts2-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2010-1870?

Update org.apache.struts:struts2-core to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-1870 is resolved across your whole dependency graph.

How do I detect CVE-2010-1870 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.struts:struts2-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2010-1870 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2010-1870 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2010-1870, including 2 documented proof-of-concept exploits on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2010-1870?

CVE-2010-1870 has an EPSS (Exploit Prediction Scoring System) score of 92.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is there exploit tooling available for CVE-2010-1870?

A Nuclei detection template exists for CVE-2010-1870, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2010-1870 published, and has it been updated?

CVE-2010-1870 was published on May 13, 2022 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2010-1870 — struts2-core

CVE-2010-1870 is a security vulnerability in org.apache.struts:struts2-core. 4 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.struts:struts2-core — see the affected versions and patch details below.

Server side object manipulation in Apache Struts

Published

May 13, 2022

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

92.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.apache.struts:struts2-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.struts:struts2-core`	all versions	2.2.1`org.apache.struts:struts2-core:2.2.1`

Affected Products

1 product · 26 configurations

Application

strutsapache

26 versions

2.0.02.0.12.0.22.0.32.0.42.0.52.0.62.0.72.0.82.0.92.0.102.0.11

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-14360remotemultiple

Struts2/XWork < 2.2.0 - Remote Command Execution

by Meder Kydyraliev · Jul 14, 2010

Exploit-DB Source

EDB-17691remotemultiple✓ Verified

Apache Struts < 2.2.0 - Remote Command Execution (Metasploit)

by Metasploit · Aug 19, 2011

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.struts:struts2-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.struts:struts2-core to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-1870 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2010-1870

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2010-1870 -u https://target

Template: ListSERV Maestro <= 9.0-8 RCE
Severity: medium
Impact: Successful exploitation of this vulnerability could allow an attacker to execute arbitrary code on the affected system.
Remediation: Upgrade to a patched version of ListSERV Maestro that is not affected by this vulnerability.

Template by ProjectDiscovery nuclei-templates (b0yd), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

OGNL provides, among other features, extensive expression evaluation capabilities. This vulnerability allows a malicious user to bypass the '#'-usage protection built into the ParametersInterceptor, thus being able to manipulate server side context objects. This behavior was already addressed in [S2-003](https://cwiki.apache.org/confluence/display/WW/S2-003), but it turned out that the resulting fix based on whitelisting acceptable parameter names closed the vulnerability only partially.

O3 Security · Impact-Aware SCA

Is CVE-2010-1870 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works