How severe is CVE-2012-6708?

CVE-2012-6708 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-2012-6708?

CVE-2012-6708 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 CVE-2012-6708?

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

How do I detect CVE-2012-6708 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 CVE-2012-6708 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-2012-6708 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2012-6708, including 1 documented proof-of-concept exploit on Exploit-DB and 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-2012-6708?

CVE-2012-6708 has an EPSS (Exploit Prediction Scoring System) score of 8.6%, placing it in the 95th 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-2012-6708?

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

CVE-2012-6708 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

Not in CISA KEV

MEDIUM severity

CVE-2012-6708 — jquery

MEDIUMFix: jquery/jquery@05531fc

CVE-2012-6708 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.webjars.npm:jquery. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.webjars.npm:jquery — see the affected versions and patch details below.

Cross-Site Scripting in jquery

Also known asGHSA-2pqj-h3vj-pqgw

Published

Jan 18, 2018

Updated

Apr 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

8.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% 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

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

22Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

jquerynpm

11.7Mdownloads / week

Description

jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.

Affected Packages

4 total 4 fixed

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

Affected Products

1 product · 1 configurations

Application

jqueryjquery

< 1.9.0

range

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.

EDB-49708webappshardware

Linksys EA7500 2.0.8.194281 - Cross-Site Scripting

by MiningOmerta · Mar 25, 2021

Exploit-DB Source

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.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-6708 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.

UbuntuMEDIUM

USN-7622-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-6708 in your dependencies?

Find it across Maven, npm, NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works