CVERadar
MEDIUM · CVSS 3.1 6.1Exploit-DBPublic PoCEPSS 86.82% (p100)Threat level 64

CVE-2019-11358: CVE-2019-11358: jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuer…

jquery · jquery · NVD published 2019-04-20 · posted 2019-04-20 · last modified 2026-06-17

What it is

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.

WeaknessCWE-1321
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N (source: [email protected])
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2019-04-20 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

Exploit-DB

  • EDB-52141: jQuery 3.3.1 - Prototype Pollution & XSS Exploit (2025-04-08)

GitHub proof-of-concept repositories

6 public repositories from 5 accounts, first seen 2019-04-20. Most starred: chrisneagu/FTC-Skystone-Dark-Angels-Romania-2020 (319 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: Exploit-DB (OffSec) · nomi-sec/PoC-in-GitHub.

No ATT&CK techniques could be mapped or inferred for this CVE yet.

How to fix it

Fixed versions

  • jquery jquery: upgrade to 3.4.0 or later
  • drupal drupal: upgrade to 7.66 or later (affected from 7.0)
  • drupal drupal: upgrade to 8.5.15 or later (affected from 8.5.0)
  • drupal drupal: upgrade to 8.6.15 or later (affected from 8.6.0)
  • backdropcms backdrop: upgrade to 1.11.9 or later (affected from 1.11.0)
  • backdropcms backdrop: upgrade to 1.12.6 or later (affected from 1.12.0)
  • oracle application express: upgrade to 19.1 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources