How severe is CVE-2007-2449?

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

Which packages are affected by CVE-2007-2449?

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

How do I fix CVE-2007-2449?

The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2007-2449. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

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

Yes. There are 1 known exploit references for CVE-2007-2449, including 1 documented proof-of-concept exploit on Exploit-DB. 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-2007-2449?

CVE-2007-2449 has an EPSS (Exploit Prediction Scoring System) score of 77.4%, 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.

Is there exploit tooling available for CVE-2007-2449?

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

CVE-2007-2449 was published on May 1, 2022 and was last updated on November 8, 2023. 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-2007-2449 — tomcat

CVE-2007-2449 is a security vulnerability in org.apache.tomcat:tomcat. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Apache Tomcat XSS Vulnerabilities in Examples Web Application

Published

May 1, 2022

Updated

Nov 8, 2023

Affected

4 pkgs

Patched

See advisory

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

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

4 pkgs affected

☕org.apache.tomcat:tomcat☕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 certain JSP files in the examples web application in Apache Tomcat 4.0.0 through 4.0.6, 4.1.0 through 4.1.36, 5.0.0 through 5.0.30, 5.5.0 through 5.5.24, and 6.0.0 through 6.0.13 allow remote attackers to inject arbitrary web script or HTML via the portion of the URI after the ; character, as demonstrated by a URI containing a snp/snoop.jsp; sequence.

Affected Packages

4 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 4.0.0	No fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.0.0	No fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.5.0	No fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0	No fix

Affected Products

1 product · 73 configurations

Application

tomcatapache

≤ 4.1.36

72 versions

4.0.04.0.14.0.24.0.34.0.44.0.55.0.05.0.15.0.25.0.35.0.45.0.5

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-30189webappsjsp✓ Verified

Apache Tomcat 6.0.13 - JSP Example Web Applications Cross-Site Scripting

by anonymous · Jun 14, 2007

Exploit-DB Source

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.
Remediation status
The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2007-2449. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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.

How to detect CVE-2007-2449

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

nuclei -id cve-2007-2449 -u https://target

Template: Apache Tomcat 4.x-7.x - Cross-Site Scripting
Severity: medium
Impact: Attackers can execute arbitrary scripts in victim browsers, leading to session hijacking, defacement, or redirection.
Remediation: Apply the latest security patches and updates from the vendor to address this vulnerability.

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

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.1.0.4.el5`	RHSA-2007:0569
Red Hat Network Satellite Server v 4.2	`jabberd-0:2.0s10-3.38.rhn`	RHSA-2008:0524
Red Hat Network Satellite Server v 5.0	`jabberd-0:2.0s10-3.38.rhn`	RHSA-2008:0261
Red Hat Network Satellite Server v 5.1	`jfreechart-0:0.9.20-3.rhn`	RHSA-2008:0630
RHAPS Version 2 for RHEL 4	`tomcat5-0:5.5.23-0jpp_4rh.4`	RHSA-2007:0876

Frequently Asked Questions

Multiple cross-site scripting (XSS) vulnerabilities in certain JSP files in the examples web application in Apache Tomcat 4.0.0 through 4.0.6, 4.1.0 through 4.1.36, 5.0.0 through 5.0.30, 5.5.0 through 5.5.24, and 6.0.0 through 6.0.13 allow remote attackers to inject arbitrary web script or HTML via the portion of the URI after the `;` character, as demonstrated by a URI containing a `snp/snoop.jsp;` sequence.

O3 Security · Impact-Aware SCA

Is CVE-2007-2449 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works