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

CVE-2019-11358

MEDIUMFix: jquery/jquery@753d591

CVE-2019-11358 is a medium-severity (CVSS 6.1) CWE-1321 vulnerability in org.webjars.npm:jquery. 16 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2019-11358 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asDRUPAL-CORE-2019-006GHSA-6c3j-c64m-qhgqPYSEC-2026-628
Published
Apr 20, 2019
Updated
Jul 15, 2026
Affected
7 pkgs
Patched
7 / 7
Exploits
16 known
Exploitation data as of Aug 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2019-11358.

EPSS Exploitation Probability

via FIRST.org ↗
87.2%probability of exploitation in next 30 days
Very High Risk0.00%
Lower risk than most CVEs100th percentile — riskier than 100% 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.

How urgent is this, really

CVE-2019-11358 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 371,256 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

7 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
17.3Mdownloads / week

Description

jQuery before 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 CVE-2019-11358 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 CVE-2019-11358 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-2019-11358. 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.

UbuntuMEDIUM

Frequently Asked Questions

jQuery before 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 CVE-2019-11358 in your dependencies?

O3 detects CVE-2019-11358 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.

CVE-2019-11358: jquery (Medium 6.1) | O3 Security