How severe is CVE-2013-1966?

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

Which products are affected by CVE-2013-1966?

Affected package information for CVE-2013-1966 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2013-1966?

Apply the apache struts security patch or hotfix for CVE-2013-1966 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2013-1966 across my infrastructure?

Inventory every apache struts deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

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

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2013-1966?

O3 detects and blocks CVE-2013-1966 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

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

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

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

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

Which products and versions are affected by CVE-2013-1966?

CVE-2013-1966 affects apache struts. Check the affected-products list on this page against your deployed version to confirm exposure.

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

CVE-2013-1966 was published on July 10, 2013 and was last updated on June 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2013-1966

Apache Struts 2 before 2.3.14.2 allows remote attackers to execute arbitrary OGNL code via a crafted request that is not properly handled when using the includeParams attribute in the…

Published

Jul 10, 2013

Updated

Jun 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

71.8%probability of exploitation in next 30 days

Very High Risk99th percentile0.00%

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.

Description

Apache Struts 2 before 2.3.14.2 allows remote attackers to execute arbitrary OGNL code via a crafted request that is not properly handled when using the includeParams attribute in the (1) URL or (2) A tag.

Affected Products

1 product · 1 configurations

Application

strutsapache

≥ 2.0.0 && < 2.3.14.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-25980remotemultiple✓ Verified

Apache Struts - includeParams Remote Code Execution (Metasploit)

by Metasploit · Jun 5, 2013

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every apache struts deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the apache struts security patch or hotfix for CVE-2013-1966 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2013-1966 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

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

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2013-1966 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2013-1966 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works