How severe is GHSA-579v-mp3v-rrw5?

No CVSS score has been assigned to GHSA-579v-mp3v-rrw5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-579v-mp3v-rrw5?

GHSA-579v-mp3v-rrw5 affects the following packages: org.webjars.npm:jquery (Maven), jquery (npm), jQuery (NuGet), jquery-rails (RubyGems). Ecosystems affected: Maven, npm, NuGet, RubyGems.

How do I fix GHSA-579v-mp3v-rrw5?

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.

How do I detect GHSA-579v-mp3v-rrw5 in my Maven, npm, NuGet, RubyGems dependencies?

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.

How do I mitigate GHSA-579v-mp3v-rrw5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-579v-mp3v-rrw5?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-579v-mp3v-rrw5 can be triaged on real exposure rather than presence alone.

Is GHSA-579v-mp3v-rrw5 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-579v-mp3v-rrw5, 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 GHSA-579v-mp3v-rrw5?

GHSA-579v-mp3v-rrw5 has an EPSS (Exploit Prediction Scoring System) score of 19.2%, 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 GHSA-579v-mp3v-rrw5?

GHSA-579v-mp3v-rrw5 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 GHSA-579v-mp3v-rrw5 published, and has it been updated?

GHSA-579v-mp3v-rrw5 was published on May 14, 2022 and was last updated on February 3, 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📦 npm.NET NuGet💎 RubyGems

Not in CISA KEV

GHSA-579v-mp3v-rrw5 — jquery

Fix: jquery/jquery@db9e023

GHSA-579v-mp3v-rrw5 is a Cross-site Scripting (XSS) vulnerability in org.webjars.npm:jquery. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.webjars.npm:jquery — see the affected versions and patch details below.

jQuery vulnerable to Cross-Site Scripting (XSS)

Also known asCVE-2011-4969

Published

May 14, 2022

Updated

Feb 3, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

19.2%probability of exploitation in next 30 days

Moderate Risk0.00%

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

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

4 pkgs affected

☕org.webjars.npm:jquery📦jquery.NETjQuery💎jquery-rails

Real-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

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.webjars.npm:jquery`	all versions	1.6.3`org.webjars.npm:jquery:1.6.3`
📦npm	`jquery`	all versions	1.6.3`npm install jquery@1.6.3`
.NETNuGet	`jQuery`	all versions	1.6.3`dotnet add package jQuery --version 1.6.3`
💎RubyGems	`jquery-rails`	all versions	1.0.16`bundle update jquery-rails --conservative`

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.

Cross-site scripting (XSS) vulnerability in jQuery before 1.6.3, when us…

github.comNVDApr 2019

Detection & mitigation playbook

Open-source dependency

Detect
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-579v-mp3v-rrw5 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-579v-mp3v-rrw5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

Ubuntu

USN-1722-1Ubuntu

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-579v-mp3v-rrw5 in your dependencies?

O3 Security finds GHSA-579v-mp3v-rrw5 across Maven, npm, NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works