# CVE-2013-1966: Arbitrary code execution in Apache Struts

> Remote attackers can execute arbitrary OGNL code via crafted requests using specific URL or A tag attributes in Apache Struts 2.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jul 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-737w-mh58-cxjp

## What is CVE-2013-1966?

CVE-2013-1966 is a critical code injection vulnerability in Apache Struts, published on 10 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2013-1966?

4 open source packages ship an affected version, including org.apache.struts.xwork:xwork-core and org.apache.struts:struts2-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.struts.xwork:xwork-core` | Maven | From 2.0.0 | 2.3.14.2 |
| `org.apache.struts.xwork:xwork-core` | Maven | From 2.0.0 | 2.3.14.2 |
| `org.apache.struts:struts2-core` | Maven | From 2.0.0 | 2.3.14.2 |
| `org.apache.struts:struts2-core` | Maven | From 2.0.0 | 2.3.14.2 |

Products: Apache Struts.

## How do I fix CVE-2013-1966?

Upgrade org.apache.struts.xwork:xwork-core to 2.3.14.2 or later.

## Is CVE-2013-1966 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-1966 exists.

Public exploit code:

- Apache Struts includeParams Remote Code Execution (metasploit)
- Apache Struts - includeParams Remote Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in Apache Struts

- [CVE-2020-17530](https://insights.sbomify.com/CVE-2020-17530/): Apache Struts Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-9791](https://insights.sbomify.com/CVE-2017-9791/): Apache Struts 1 Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2017-5638](https://insights.sbomify.com/CVE-2017-5638/): Apache Struts Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-0391](https://insights.sbomify.com/CVE-2012-0391/): Apache Struts 2 Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2018-11776](https://insights.sbomify.com/CVE-2018-11776/): Apache Struts Remote Code Execution (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1966 and fix it if it is affected.

What it is: CVE-2013-1966 is a critical code injection vulnerability in Apache Struts, published on 10 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-1966 exists.

Affected packages and fixed versions:
- org.apache.struts.xwork:xwork-core (Maven): affected from 2.0.0; fixed in 2.3.14.2
- org.apache.struts.xwork:xwork-core (Maven): affected from 2.0.0; fixed in 2.3.14.2
- org.apache.struts:struts2-core (Maven): affected from 2.0.0; fixed in 2.3.14.2
- org.apache.struts:struts2-core (Maven): affected from 2.0.0; fixed in 2.3.14.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-1966/ (Markdown: https://insights.sbomify.com/CVE-2013-1966/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-1966
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-1966
- OSV: https://osv.dev/vulnerability/CVE-2013-1966

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-1966/
Summaries are generated and may contain mistakes; the official description above is the record.