How severe is CVE-2013-1965?

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

Which packages are affected by CVE-2013-1965?

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

How do I fix CVE-2013-1965?

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-1965 is resolved across your whole dependency graph.

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

No public exploit code has been indexed for CVE-2013-1965 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-1965?

CVE-2013-1965 has an EPSS (Exploit Prediction Scoring System) score of 93.5%, 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.

What type of vulnerability is CVE-2013-1965?

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

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

CVE-2013-1965 was published on May 14, 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-2013-1965 — struts2-core

Fix: apache/struts@7e6f641

CVE-2013-1965 is a Code Injection vulnerability in org.apache.struts:struts2-core. EPSS puts its 30-day exploitation probability at 93.5% (100th percentile). A fix is available for org.apache.struts:struts2-core — see the affected versions and patch details below.

Improper Control of Generation of Code in Apache Struts

Published

May 14, 2022

Updated

Dec 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

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

Apache Struts Showcase App 2.0.0 through 2.3.13, as used in Struts 2 before 2.3.14.3, allows remote attackers to execute arbitrary OGNL code via a crafted parameter name that is not properly handled when invoking a redirect.

Affected Packages

1 total 1 fixed

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

Affected Products

2 products · 2 configurations

Application

strutsapache

≥ 2.0.0 && < 2.3.14.1

range

Application

struts2-showcaseapache

≥ 2.0.0 && ≤ 2.3.13

range

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-1965 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.

How to detect CVE-2013-1965

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

nuclei -id cve-2013-1965 -u https://target

Template: Apache Struts2 S2-012 RCE
Severity: critical
Impact: Successful exploitation of this vulnerability can lead to remote code execution on the affected server.
Remediation: Developers should immediately upgrade to Struts 2.3.14.3 or later.

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-1965 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works