How severe is CVE-2006-0254?

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

Which packages are affected by CVE-2006-0254?

CVE-2006-0254 affects the following packages: geronimo:geronimo-console-standard (Maven). Ecosystems affected: Maven.

How do I fix CVE-2006-0254?

Update geronimo:geronimo-console-standard to 1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-0254 is resolved across your whole dependency graph.

How do I detect CVE-2006-0254 in my Maven dependencies?

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

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

Yes. There are 5 known exploit references for CVE-2006-0254, including 2 documented proof-of-concept exploits on Exploit-DB and 3 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-2006-0254?

CVE-2006-0254 has an EPSS (Exploit Prediction Scoring System) score of 32.2%, placing it in the 98th 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.

When was CVE-2006-0254 published, and has it been updated?

CVE-2006-0254 was published on May 1, 2022 and was last updated on December 5, 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-2006-0254 — geronimo-console-standard

CVE-2006-0254 is a security vulnerability in geronimo:geronimo-console-standard. 5 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for geronimo:geronimo-console-standard — see the affected versions and patch details below.

Apache Geronimo console 1.0 vulnerable to cross-site scripting

Published

May 1, 2022

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

5 known

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

EPSS Exploitation Probability

via FIRST.org ↗

32.2%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕geronimo:geronimo-console-standard

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 Apache Geronimo 1.0 allow remote attackers to inject arbitrary web script or HTML via the (1) time parameter to cal2.jsp and (2) any invalid parameter, which causes an XSS when the log file is viewed by the Web-Access-Log viewer. Version 1.1 contains fixes for these issues.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`geronimo:geronimo-console-standard`	all versions	1.1`geronimo:geronimo-console-standard:1.1`

Affected Products

1 product · 1 configurations

Application

geronimoapache

1 version

1.0

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-27096remotemultiple✓ Verified

Apache Geronimo 1.0 - Error Page Cross-Site Scripting

by Oliver Karow · Jan 16, 2006

Exploit-DB Source

EDB-27095remotemultiple✓ Verified

Apache Tomcat / Geronimo 1.0 - 'Sample Script cal2.jsp?time' Cross-Site Scripting

by Oliver Karow · Jan 16, 2006

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 geronimo:geronimo-console-standard, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update geronimo:geronimo-console-standard to 1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-0254 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 Application Server 3AS	see advisory	RHSA-2006:0592
Red Hat Application Server v2 4AS	see advisory	RHSA-2006:0161
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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2006-0254 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works