# CVE-2007-2449: Apache Tomcat XSS Vulnerabilities in Examples Web Application > Remote attackers can inject arbitrary web script via crafted URIs in the default examples application, requiring user interaction to execute. - **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 14 Jun 2007 - **Updated:** 7 Aug 2024 - **Also known as:** GHSA-hc39-rjwp-qffq ## What is CVE-2007-2449? CVE-2007-2449 is a medium-severity cross-site scripting vulnerability in Apache Tomcat, published on 14 Jun 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official 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. ## Which versions are affected by CVE-2007-2449? 8 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 4.0.0 to 4.0.6 | None | | `org.apache.tomcat:tomcat` | Maven | From 4.0.0 to 4.0.6 | None | | `org.apache.tomcat:tomcat` | Maven | From 5.0.0 to 5.0.30 | None | | `org.apache.tomcat:tomcat` | Maven | From 5.0.0 to 5.0.30 | None | | `org.apache.tomcat:tomcat` | Maven | From 5.5.0 to 5.5.24 | None | | `org.apache.tomcat:tomcat` | Maven | From 5.5.0 to 5.5.24 | None | | `org.apache.tomcat:tomcat` | Maven | From 6.0.0 to 6.0.13 | None | | `org.apache.tomcat:tomcat` | Maven | From 6.0.0 to 6.0.13 | None | Products: Apache Tomcat. ## How do I fix CVE-2007-2449? Upgrade to a fixed version. ## Is CVE-2007-2449 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2449 exists. Public exploit code: - Apache Tomcat 6.0.13 - JSP Example Web Applications Cross-Site Scripting (exploitdb) - Apache Tomcat 4.x-7.x - Cross-Site Scripting (nuclei): http/cves/2007/CVE-2007-2449.yaml ## 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-2007-2449 and fix it if it is affected. What it is: CVE-2007-2449 is a medium-severity cross-site scripting vulnerability in Apache Tomcat, published on 14 Jun 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2449 exists. Affected packages and fixed versions: - org.apache.tomcat:tomcat (Maven): affected from 4.0.0 up to 4.0.6; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 4.0.0 up to 4.0.6; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 5.0.0 up to 5.0.30; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 5.0.0 up to 5.0.30; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 5.5.0 up to 5.5.24; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 5.5.0 up to 5.5.24; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 6.0.0 up to 6.0.13; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 6.0.0 up to 6.0.13; no fix listed 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-2007-2449/ (Markdown: https://insights.sbomify.com/CVE-2007-2449/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2007-2449 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-2449 - OSV: https://osv.dev/vulnerability/CVE-2007-2449 --- From sbomify Insights: https://insights.sbomify.com/CVE-2007-2449/ Summaries are generated and may contain mistakes; the official description above is the record.