How severe is CVE-2011-0013?

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

Which packages are affected by CVE-2011-0013?

CVE-2011-0013 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2011-0013?

Update org.apache.tomcat:tomcat to 5.5.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-0013 is resolved across your whole dependency graph.

How do I detect CVE-2011-0013 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2011-0013 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2011-0013, including 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-2011-0013?

CVE-2011-0013 has an EPSS (Exploit Prediction Scoring System) score of 10.0%, placing it in the 96th 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. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2011-0013?

CVE-2011-0013 is classified as Cross-site Scripting (XSS) (CWE-79). 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-2011-0013 published, and has it been updated?

CVE-2011-0013 was published on May 3, 2022 and was last updated on February 21, 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-2011-0013 — tomcat

Fix: apache/tomcat@58223c5

CVE-2011-0013 is a Cross-site Scripting (XSS) vulnerability in org.apache.tomcat:tomcat. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Improper Neutralization of Input During Web Page Generation in Apache Tomcat

Published

May 3, 2022

Updated

Feb 21, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

10.0%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

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

Multiple cross-site scripting (XSS) vulnerabilities in the HTML Manager Interface in Apache Tomcat 5.5 before 5.5.32, 6.0 before 6.0.30, and 7.0 before 7.0.6 allow remote attackers to inject arbitrary web script or HTML, as demonstrated via the display-name tag.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.5.0&&< 5.5.32	5.5.32`org.apache.tomcat:tomcat:5.5.32`
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.30	6.0.30`org.apache.tomcat:tomcat:6.0.30`
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.6	7.0.6`org.apache.tomcat:tomcat:7.0.6`

Affected Products

1 product · 65 configurations

Application

tomcatapache

65 versions

5.5.05.5.15.5.25.5.35.5.45.5.55.5.65.5.75.5.85.5.95.5.105.5.11

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.

Multiple cross-site scripting (XSS) vulnerabilities in the HTML Manager …

securitytracker.comNVDMar 2019

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.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat to 5.5.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-0013 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux 5	`tomcat5-0:5.5.23-0jpp.22.el5_7`	RHSA-2011:1845
Red Hat Enterprise Linux 6	`tomcat6-0:6.0.24-33.el6`	RHSA-2011:0791
Red Hat JBoss Enterprise Web Server 1 for RHEL 5	`ant-0:1.7.1-13.jdk6.ep5.el5`	RHSA-2011:0897
Red Hat JBoss Web Server 1.0	see advisory	RHSA-2011:0896

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-0013 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works