How severe is CVE-2002-1533?

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

Which packages are affected by CVE-2002-1533?

CVE-2002-1533 affects the following packages: org.mortbay.jetty:jetty (Maven). Ecosystems affected: Maven.

How do I fix CVE-2002-1533?

Update org.mortbay.jetty:jetty to 4.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2002-1533 is resolved across your whole dependency graph.

How do I detect CVE-2002-1533 in my Maven dependencies?

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

How do I mitigate CVE-2002-1533 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-2002-1533 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2002-1533, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations 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-2002-1533?

CVE-2002-1533 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 84th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2002-1533 published, and has it been updated?

CVE-2002-1533 was published on April 30, 2022 and was last updated on November 28, 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-2002-1533 — jetty

CVE-2002-1533 is a security vulnerability in org.mortbay.jetty:jetty. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.mortbay.jetty:jetty — see the affected versions and patch details below.

Jetty Javascript Inclusion Vulnerability

Published

Apr 30, 2022

Updated

Nov 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.mortbay.jetty:jetty

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

Cross-site scripting (XSS) vulnerability in Jetty JSP servlet engine allows remote attackers to insert arbitrary HTML or script via an HTTP request to a .jsp file whose name contains the malicious script and some encoded linefeed characters (%0a).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.mortbay.jetty:jetty`	all versions	4.1.1`org.mortbay.jetty:jetty:4.1.1`

Affected Products

1 product · 1 configurations

Application

jettyjetty

1 version

4.1.0_rc4

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

Jetty 4.1 Servlet Engine - Cross-Site Scripting

by Skinnay · Sep 28, 2002

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.mortbay.jetty:jetty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.mortbay.jetty:jetty to 4.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2002-1533 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2002-1533 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works