# CVE-2013-4444: Apache Tomcat Unrestricted file upload vulnerability

> Remote attackers can execute arbitrary code by uploading a JSP file in Apache Tomcat when specific JMX configurations are enabled.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Sep 2014
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-h6c8-x5r3-pm88

## What is CVE-2013-4444?

CVE-2013-4444 is a medium-severity vulnerability in Apache Tomcat, published on 12 Sep 2014. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in Apache Tomcat 7.x before 7.0.40, in certain situations involving outdated java.io.File code and a custom JMX configuration, allows remote attackers to execute arbitrary code by uploading and accessing a JSP file.

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

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

2 open source packages ship an affected version, including org.apache.tomcat:tomcat. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat:tomcat` | Maven | From 7.0 | 7.0.40 |
| `org.apache.tomcat:tomcat` | Maven | From 7.0 | 7.0.40 |

Products: Apache Tomcat.

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

Upgrade org.apache.tomcat:tomcat to 7.0.40 or later.

## Is CVE-2013-4444 being exploited?

There is no known exploitation of CVE-2013-4444 in the wild and no public exploit code.

## Other vulnerabilities in Apache Tomcat

- [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild)
- [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4444 is a medium-severity vulnerability in Apache Tomcat, published on 12 Sep 2014. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4444 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tomcat:tomcat (Maven): affected from 7.0; fixed in 7.0.40
- org.apache.tomcat:tomcat (Maven): affected from 7.0; fixed in 7.0.40

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-4444/ (Markdown: https://insights.sbomify.com/CVE-2013-4444/index.md)
```

## Sources

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

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