How severe is CVE-2013-2134?

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

Which packages are affected by CVE-2013-2134?

CVE-2013-2134 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-2013-2134?

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

How do I detect CVE-2013-2134 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-2013-2134 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2013-2134 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2013-2134, including 1 documented proof-of-concept exploit on Exploit-DB. 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-2013-2134?

CVE-2013-2134 has an EPSS (Exploit Prediction Scoring System) score of 70.2%, 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-2013-2134?

CVE-2013-2134 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.

When was CVE-2013-2134 published, and has it been updated?

CVE-2013-2134 was published on May 14, 2022 and was last updated on December 5, 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-2013-2134 — struts2-core

Fix: apache/struts@01e6b25

CVE-2013-2134 is a Code Injection vulnerability in org.apache.struts:struts2-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.struts:struts2-core — see the affected versions and patch details below.

Arbitrary code execution in Apache Struts 2

Published

May 14, 2022

Updated

Dec 5, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

70.2%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

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

Apache Struts 2 before 2.3.14.3 allows remote attackers to execute arbitrary OGNL code via a request with a crafted action name that is not properly handled during wildcard matching, a different vulnerability than CVE-2013-2135.

Affected Packages

2 total 2 fixed

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

Affected Products

1 product · 1 configurations

Application

strutsapache

≥ 2.0.0 && < 2.3.14.3

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

Apache Struts - OGNL Expression Injection

by Jon Passki · Jun 5, 2013

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.14.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2134 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-2134 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works