How severe is CVE-2014-1904?

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

Which packages are affected by CVE-2014-1904?

CVE-2014-1904 affects the following packages: org.springframework:spring-webmvc (Maven), org.springframework:spring-webmvc (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-1904?

Update org.springframework:spring-webmvc to 3.2.8.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-1904 is resolved across your whole dependency graph.

How do I detect CVE-2014-1904 in my Maven dependencies?

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

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

No public exploit code has been indexed for CVE-2014-1904 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-2014-1904?

CVE-2014-1904 has an EPSS (Exploit Prediction Scoring System) score of 6.9%, placing it in the 94th 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-2014-1904?

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

CVE-2014-1904 was published on March 20, 2014 and was last updated on April 16, 2026. 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-2014-1904 — spring-webmvc

Fix: spring-projects/spring-framework@741b4b2

CVE-2014-1904 is a Cross-site Scripting (XSS) vulnerability in org.springframework:spring-webmvc. A fix is available for org.springframework:spring-webmvc — see the affected versions and patch details below.

Improper Neutralization of Input During Web Page Generation in Spring Framework

Also known asGHSA-ff7p-jqjm-v66h

Published

Mar 20, 2014

Updated

Apr 16, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

6.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕org.springframework:spring-webmvc☕org.springframework:spring-webmvc

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 web/servlet/tags/form/FormTag.java in Spring MVC in Spring Framework 3.0.0 before 3.2.8 and 4.0.0 before 4.0.2 allows remote attackers to inject arbitrary web script or HTML via the requested URI in a default action.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework:spring-webmvc`	≥ 3.0.0&&< 3.2.8.RELEASE	3.2.8.RELEASE`org.springframework:spring-webmvc:3.2.8.RELEASE`
☕Maven	`org.springframework:spring-webmvc`	≥ 4.0.0&&< 4.0.2.RELEASE	4.0.2.RELEASE`org.springframework:spring-webmvc:4.0.2.RELEASE`

Affected Products

1 product · 2 configurations

Application

spring frameworkpivotal_software

≥ 4.0.0 && < 4.0.2

range

Detection & mitigation playbook

Open-source dependency

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

The Red Hat Security Response Team has rated this issue as having Moderate security impact. OpenShift Enterprise 1 is currently in the Production 1 phase of its lifecycle, as such this issue is not currently planned to be addressed in future updates. For additional information, refer to the Satellite Life Cycle:…

RHSA-2014:0401Red Hat JBoss A-MQ 6.1 RHSA-2014:0400Red Hat JBoss Fuse 6.1

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-1904 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works