Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven📦 npm.NET NuGet🐘 Packagist🐍 PyPI

GHSA-6c3j-c64m-qhgq

MEDIUM

XSS in jQuery as used in Drupal, Backdrop CMS, and other products

Also known asCVE-2019-11358DRUPAL-CORE-2019-006PYSEC-2026-628SNYK-JS-JQUERY-174006
Published
Apr 26, 2019
Updated
Jul 8, 2026
Affected
7 pkgs
Patched
7 / 7
Exploits
16 known

Blast Radius

7 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

jquerynpm
17.8Mdownloads / week

Description

jQuery from 1.1.4 until 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.

Affected Packages

7 total 7 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.webjars.npm:jquery1.1.4&&< 3.4.03.4.0
📦npmjquery1.1.4&&< 3.4.03.4.0
.NETNuGetjQuery1.1.4&&< 3.4.03.4.0
🐘Packagistmaximebf/debugbarall versions1.19.0
🐍PyPIdjango2.0a1&&< 2.1.92.1.9
🐍PyPIdjango2.2a1&&< 2.2.22.2.2
Exploits & PoCs
16

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52141webappsmultiple

jQuery 3.3.1 - Prototype Pollution & XSS Exploit

by xOryus · Apr 8, 2025

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update org.webjars.npm:jquery to 3.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6c3j-c64m-qhgq is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-6c3j-c64m-qhgq 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 GHSA-6c3j-c64m-qhgq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

jQuery from 1.1.4 until 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles `jQuery.extend(true, {}, ...)` because of `Object.prototype` pollution. If an unsanitized source object contained an enumerable `__proto__` property, it could extend the native `Object.prototype`.
O3 Security · Impact-Aware SCA

Is GHSA-6c3j-c64m-qhgq in your dependencies?

O3 detects GHSA-6c3j-c64m-qhgq 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.