CVE-2011-4969

jQuery vulnerable to Cross-Site Scripting (XSS)

Verified by Precogs Threat Research
Last Updated: Feb 3, 2026
Base Score
7.5HIGH

Executive Summary

CVE-2011-4969 is a high severity vulnerability affecting appsec. It is classified as an undisclosed flaw. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"Precogs AI Analysis Engine identifies web application vulnerabilities through semantic code analysis, detecting injection flaws, broken authentication, and insecure data flows across your entire codebase."

Exploit Probability
Elevated (52%)
Public POC
Undisclosed
Exploit Probability
Elevated (52%)
Public POC
Available
Affected Assets
appsecNVD Database

What is this vulnerability?

CVE-2011-4969 is categorized as a critical Cross-Site Scripting (XSS) flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

Cross-site scripting (XSS) vulnerability in jQuery before 1.6.3, when using location.hash to select elements, allows remote attackers to inject arbitrary w.

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score7.5 (HIGH)
Vector StringN/A
PublishedMay 14, 2022
Last ModifiedFebruary 3, 2026
Related CWEsN/A

Impact on Systems

Session Hijacking: Attackers can steal active user session tokens (cookies) to impersonate the victim.

Phishing Execution: Malicious scripts can dynamically alter DOM content to present fraudulent login forms.

Worm Propagation: Stored XSS can spread autonomously as users visit the infected page.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Output Encoding Implement strict context-aware output encoding (HTML, JavaScript, Attribute, CSS) before rendering user data.

2. Content Security Policy (CSP) Deploy a rigorous CSP header to restrict script execution exclusively to trusted domains.

3. Framework Defenses Utilize native UI framework protections (e.g., React DOM escaping) and avoid dangerouslySetInnerHTML.

Vulnerability Signature

// Example DOM-based XSS vulnerability
const user_input = new URLSearchParams(window.location.search).get('q');
// VULNERABLE: Direct insertion into innerHTML
document.getElementById('results').innerHTML = "Results for: " + user_input; 

// EXPLOIT PAYLOAD: ?q=\<img src=x onerror=alert(document.cookie)\>

References and Sources