How severe is CVE-2015-9251?

CVE-2015-9251 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-2015-9251?

CVE-2015-9251 affects the following packages: org.webjars.npm:jquery (Maven), org.webjars.npm:jquery (Maven), jquery (npm), jquery (npm), jQuery (NuGet), jQuery (NuGet), jquery-rails (RubyGems). Ecosystems affected: Maven, npm, NuGet, RubyGems.

How do I fix CVE-2015-9251?

Update org.webjars.npm:jquery to 1.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-9251 is resolved across your whole dependency graph.

How do I detect CVE-2015-9251 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2015-9251 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 CVE-2015-9251?

O3 pinpoints whether CVE-2015-9251 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2015-9251 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2015-9251, 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 type of vulnerability is CVE-2015-9251?

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

CVE-2015-9251 was published on January 18, 2018 and was last updated on April 10, 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

CVE-2015-9251

MEDIUM

Cross-Site Scripting (XSS) in jquery

Also known asGHSA-rmxg-73gg-4p98

Published

Jan 18, 2018

Updated

Apr 10, 2026

Affected

7 pkgs

Patched

7 / 7

Exploits

2 known

Blast Radius

7 pkgs affected

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

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, npm packages — download data is not available via public APIs for these ecosystems.

Description

jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.

Affected Packages

7 total 7 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.webjars.npm:jquery`	all versions	1.12.2
☕Maven	`org.webjars.npm:jquery`	≥ 1.12.3&&< 3.0.0	3.0.0
📦npm	`jquery`	all versions	1.12.2
📦npm	`jquery`	≥ 1.12.3&&< 3.0.0	3.0.0
.NETNuGet	`jQuery`	all versions	1.12.2
.NETNuGet	`jQuery`	≥ 1.12.3&&< 3.0.0	3.0.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.

jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks …

github.comGithubDec 2018

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.webjars.npm:jquery to 1.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-9251 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 pinpoints whether CVE-2015-9251 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2015-9251. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.

O3 Security · Impact-Aware SCA

Is CVE-2015-9251 in your dependencies?

O3 detects CVE-2015-9251 across Maven, npm, NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works