How severe is CVE-2017-17837?

CVE-2017-17837 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-17837?

CVE-2017-17837 affects the following packages: org.apache.deltaspike.modules:jsf-module-project (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-17837?

Update org.apache.deltaspike.modules:jsf-module-project to 1.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-17837 is resolved across your whole dependency graph.

How do I detect CVE-2017-17837 in my Maven dependencies?

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

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

Yes. There are 1 known exploit references for CVE-2017-17837, including 1 in-the-wild exploitation 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-2017-17837?

CVE-2017-17837 has an EPSS (Exploit Prediction Scoring System) score of 4.5%, placing it in the 91th 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-2017-17837?

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

CVE-2017-17837 was published on January 4, 2018 and was last updated on October 24, 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

MEDIUM severity

CVE-2017-17837 — jsf-module-project

MEDIUMFix: apache/deltaspike@4e25023

CVE-2017-17837 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.apache.deltaspike.modules:jsf-module-project. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.deltaspike.modules:jsf-module-project — see the affected versions and patch details below.

Cross-site Scripting in Apache DeltaSpike

Also known asGHSA-4q23-g7mf-xp98

Published

Jan 4, 2018

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

4.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.apache.deltaspike.modules:jsf-module-project

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

The Apache DeltaSpike-JSF 1.8.0 module has a XSS injection leak in the windowId handling. The default size of the windowId get's cut off after 10 characters (by default), so the impact might be limited. A fix got applied and released in Apache deltaspike-1.8.1.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.deltaspike.modules:jsf-module-project`	all versions	1.8.1`org.apache.deltaspike.modules:jsf-module-project:1.8.1`

Affected Products

1 product · 1 configurations

Application

deltaspikeapache

1 version

1.8.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.

The Apache DeltaSpike-JSF 1.8.0 module has a XSS injection leak in the w…

issues.apache.orgNVDAug 2021

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.deltaspike.modules:jsf-module-project, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.deltaspike.modules:jsf-module-project to 1.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-17837 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-2017-17837 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works