How severe is CVE-2014-0094?

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

Which packages are affected by CVE-2014-0094?

CVE-2014-0094 affects the following packages: org.apache.struts:struts2-core (Maven), org.apache.struts.xwork:xwork-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-0094?

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

How do I detect CVE-2014-0094 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-2014-0094 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-2014-0094 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2014-0094, including 2 documented proof-of-concept exploits on Exploit-DB and 1 in-the-wild exploitation 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-2014-0094?

CVE-2014-0094 has an EPSS (Exploit Prediction Scoring System) score of 99.4%, 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.

When was CVE-2014-0094 published, and has it been updated?

CVE-2014-0094 was published on May 14, 2022 and was last updated on December 6, 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-2014-0094 — struts2-core

Fix: apache/struts@2e2da29

CVE-2014-0094 is a security vulnerability in org.apache.struts:struts2-core. 3 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.

ClassLoader manipulation in Apache Struts

Published

May 14, 2022

Updated

Dec 6, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

3 known

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

EPSS Exploitation Probability

via FIRST.org ↗

99.4%probability of exploitation in next 30 days

Very High Risk-0.18%

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

2 pkgs affected

☕org.apache.struts:struts2-core☕org.apache.struts.xwork:xwork-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 ParametersInterceptor in Apache Struts before 2.3.16.2 allows remote attackers to "manipulate" the ClassLoader via the class parameter, which is passed to the getClass method.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.struts:struts2-core`	≥ 2.0.0&&< 2.3.16.2	2.3.16.2`org.apache.struts:struts2-core:2.3.16.2`
☕Maven	`org.apache.struts.xwork:xwork-core`	≥ 2.0.0&&< 2.3.16.2	2.3.16.2`org.apache.struts.xwork:xwork-core:2.3.16.2`

Affected Products

1 product · 1 configurations

Application

strutsapache

≥ 2.0.0 && < 2.3.16.1

range

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-41690remotemultiple✓ Verified

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

by Metasploit · Mar 6, 2014

Exploit-DB Source

EDB-33142remotemultiple✓ Verified

Apache Struts - ClassLoader Manipulation Remote Code Execution (Metasploit)

by Metasploit · May 2, 2014

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.3.16.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0094 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.

Frequently Asked Questions

The ParametersInterceptor in Apache Struts before 2.3.16.2 allows remote attackers to "manipulate" the ClassLoader via the class parameter, which is passed to the getClass method.

O3 Security · Impact-Aware SCA

Is CVE-2014-0094 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works