CVE-2020-5259 | Prototype Pollution in Dojox

Exp

In affected versions of dojox (NPM package), the jqMix method is vulnerable to Prototype Pollution. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. This has been patched in versions 1.11.10, 1.12.8, 1.13.7, 1.14.6, 1.15.3 and 1.16.2

Published: 2020-03-10 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-5259 is rated High Exploit Risk (74.7/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.98%). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +1.70% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2020-5259

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2020-5259

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.28% 1.98% +1.70%
2 2025-12-24 0.36% 0.28% -0.09%
3 2025-11-21 — 0.36% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-5259

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.7 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.3 5.8 [email protected]
8.6 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 4.0 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2020-5259

GitHub Security Advisory for CVE-2020-5259

OS Trackers for CVE-2020-5259

vendor priority summary link
debian not yet assigned CVE-2020-5259 not yet assigned priority: Debian including 1 source packages (dojo), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-5259
ubuntu medium CVE-2020-5259 medium priority: Ubuntu including 1 source packages (dojo), 17 status rows across 17 suites (bionic, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 11, needs-triage 4, DNE 1, ignored 1. https://ubuntu.com/security/CVE-2020-5259

Affected software / configurations for CVE-2020-5259

Vendor Product Version Raw CPE
linuxfoundation dojox < 1.11.10 cpe:2.3:a:linuxfoundation:dojox:*:*:*:*:*:node.js:*:*
linuxfoundation dojox >= 1.12.0, < 1.12.8 cpe:2.3:a:linuxfoundation:dojox:*:*:*:*:*:node.js:*:*
linuxfoundation dojox >= 1.13.0, < 1.13.7 cpe:2.3:a:linuxfoundation:dojox:*:*:*:*:*:node.js:*:*
linuxfoundation dojox >= 1.14.0, < 1.14.6 cpe:2.3:a:linuxfoundation:dojox:*:*:*:*:*:node.js:*:*
linuxfoundation dojox >= 1.15.0, < 1.15.3 cpe:2.3:a:linuxfoundation:dojox:*:*:*:*:*:node.js:*:*
linuxfoundation dojox >= 1.16.0, < 1.16.2 cpe:2.3:a:linuxfoundation:dojox:*:*:*:*:*:node.js:*:*

References for CVE-2020-5259

cvelogic Threat Intelligence