How severe is CVE-2009-0038?

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

Which packages are affected by CVE-2009-0038?

CVE-2009-0038 affects the following packages: org.apache.geronimo.plugins:console (Maven). Ecosystems affected: Maven.

How do I fix CVE-2009-0038?

Update org.apache.geronimo.plugins:console to 2.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-0038 is resolved across your whole dependency graph.

How do I detect CVE-2009-0038 in my Maven dependencies?

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

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

Yes. There are 4 known exploit references for CVE-2009-0038, including 2 documented proof-of-concept exploits 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-2009-0038?

CVE-2009-0038 has an EPSS (Exploit Prediction Scoring System) score of 18.0%, placing it in the 97th 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-2009-0038?

CVE-2009-0038 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-2009-0038 published, and has it been updated?

CVE-2009-0038 was published on May 2, 2022 and was last updated on December 3, 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-2009-0038 — console

Fix: apache/geronimo@aa0c2c2

CVE-2009-0038 is a Cross-site Scripting (XSS) vulnerability in org.apache.geronimo.plugins:console. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.geronimo.plugins:console — see the affected versions and patch details below.

Apache Geronimo Application Server multiple cross-site scripting (XSS) vulnerabilities

Published

May 2, 2022

Updated

Dec 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

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

EPSS Exploitation Probability

via FIRST.org ↗

18.0%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.apache.geronimo.plugins:console

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 web administration console in Apache Geronimo Application Server 2.1 through 2.1.3 allow remote attackers to inject arbitrary web script or HTML via the (1) name, (2) ip, (3) username, or (4) description parameter to console/portal/Server/Monitoring; or (5) the PATH_INFO to the default URI under console/portal/.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.geronimo.plugins:console`	≥ 2.1.0&&< 2.1.4	2.1.4`org.apache.geronimo.plugins:console:2.1.4`

Affected Products

1 product · 4 configurations

Application

geronimoapache

4 versions

2.12.1.12.1.22.1.3

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

Apache Geronimo 2.1.x - '/console/portal/' URI Cross-Site Scripting

by DSecRG · Apr 16, 2009

Exploit-DB Source

EDB-32920remotemultiple✓ Verified

Apache Geronimo 2.1.x - '/console/portal/Server/Monitoring' Multiple Cross-Site Scripting Vulnerabilities

by DSecRG · Apr 16, 2009

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.geronimo.plugins:console, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.geronimo.plugins:console to 2.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-0038 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-2009-0038 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works