How severe is CVE-2013-4204?

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

Which packages are affected by CVE-2013-4204?

CVE-2013-4204 affects the following packages: com.google.gwt:gwt (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-4204?

Update com.google.gwt:gwt to 2.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4204 is resolved across your whole dependency graph.

How do I detect CVE-2013-4204 in my Maven dependencies?

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

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

No public exploit code has been indexed for CVE-2013-4204 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-4204?

CVE-2013-4204 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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.

What type of vulnerability is CVE-2013-4204?

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

CVE-2013-4204 was published on May 17, 2022 and was last updated on December 6, 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-2013-4204 — gwt

CVE-2013-4204 is a Cross-site Scripting (XSS) vulnerability in com.google.gwt:gwt. A fix is available for com.google.gwt:gwt — see the affected versions and patch details below.

Improper Neutralization of Input During Web Page Generation in Google Web Toolkit

Published

May 17, 2022

Updated

Dec 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕com.google.gwt:gwt

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 JUnit files in the GWTTestCase in Google Web Toolkit (GWT) before 2.5.1 RC1 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.google.gwt:gwt`	all versions	2.5.1`com.google.gwt:gwt:2.5.1`

Affected Products

1 product · 30 configurations

Application

web toolkitgoogle

≤ 2.5.0

23 versions

1.4.601.5.01.5.11.5.21.5.31.6.21.6.31.6.41.7.01.7.12.0.02.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.google.gwt:gwt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.google.gwt:gwt to 2.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4204 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-2013-4204 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works