How severe is CVE-2012-0394?

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

Which packages are affected by CVE-2012-0394?

CVE-2012-0394 affects the following packages: org.apache.struts.xwork:xwork-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-0394?

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

How do I detect CVE-2012-0394 in my Maven dependencies?

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

How do I mitigate CVE-2012-0394 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.

How does O3 Security protect against CVE-2012-0394?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2012-0394 can be triaged on real exposure rather than presence alone.

Is CVE-2012-0394 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2012-0394, including 2 documented proof-of-concept exploits on Exploit-DB and 3 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-2012-0394?

CVE-2012-0394 has an EPSS (Exploit Prediction Scoring System) score of 72.9%, placing it in the 99th 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.

What type of vulnerability is CVE-2012-0394?

CVE-2012-0394 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2012-0394?

A Nuclei detection template exists for CVE-2012-0394, 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-2012-0394 published, and has it been updated?

CVE-2012-0394 was published on May 4, 2022 and was last updated on December 3, 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-2012-0394 — xwork-core

Fix: apache/struts@34c80da

CVE-2012-0394 is a Code Injection vulnerability in org.apache.struts.xwork:xwork-core. 5 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.struts.xwork:xwork-core — see the affected versions and patch details below.

Apache Struts's DebuggingInterceptor component allows remote code execution in developer mode

Published

May 4, 2022

Updated

Dec 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

5 known

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

EPSS Exploitation Probability

via FIRST.org ↗

72.9%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕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 DebuggingInterceptor component in Apache Struts before 2.3.1.1, when developer mode is used, allows remote attackers to execute arbitrary commands via unspecified vectors. NOTE: the vendor characterizes this behavior as not "a security vulnerability itself."

Affected Packages

1 total 1 fixed

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

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-31434remotejava✓ Verified

Apache Struts - Developer Mode OGNL Execution (Metasploit)

by Metasploit · Feb 5, 2014

Exploit-DB Source

EDB-18329webappsmultiple✓ Verified

Apache Struts 2 < 2.3.1 - Multiple Vulnerabilities

by SEC Consult · Jan 6, 2012

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.xwork:xwork-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.struts.xwork:xwork-core to 2.3.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-0394 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 O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2012-0394 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2012-0394. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

How to detect CVE-2012-0394

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

nuclei -id cve-2012-0394 -u https://target

Template: Apache Struts <2.3.1.1 - Remote Code Execution
Severity: medium
Impact: Successful exploitation of this vulnerability allows remote attackers to execute arbitrary code on the affected server.
Remediation: Upgrade Apache Struts to a version higher than 2.3.1.1 or apply the necessary patches.

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-0394 in your dependencies?

O3 Security finds CVE-2012-0394 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works