jQuery vulnerable to Cross-Site Scripting (XSS)GHSA-579v-mp3v-rrw5
Fix: jquery/jquery@db9e023GHSA-579v-mp3v-rrw5 is a Cross-site Scripting (XSS) vulnerability in org.webjars.npm:jquery. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.webjars.npm:jquery — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
org.webjars.npm:jquery📦jquery.NETjQuery💎jquery-railsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, npm, NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Cross-site scripting (XSS) vulnerability in jQuery before 1.6.3, when using location.hash to select elements, allows remote attackers to inject arbitrary web script or HTML via a crafted tag.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.webjars.npm:jquery | all versions | 1.6.3org.webjars.npm:jquery:1.6.3 |
| 📦npm | jquery | all versions | 1.6.3npm install jquery@1.6.3 |
| .NETNuGet | jQuery | all versions | 1.6.3dotnet add package jQuery --version 1.6.3 |
| 💎RubyGems | jquery-rails | all versions | 1.0.16bundle update jquery-rails --conservative |
Affected Products
jqueryjqueryResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars.npm:jquery, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.webjars.npm:jquery to 1.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-579v-mp3v-rrw5 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
Is GHSA-579v-mp3v-rrw5 in your dependencies?
Find it across Maven, npm, NuGet, including transitive dependencies.