Skip to content
Fencer Intel
high 7.7

CVE-2020-5259 json

Prototype Pollution in Dojox

published 2020-03-10 6 y ago modified 2026-07-08 4 mo ago also GHSA-3hw5-q855-g6cw , EUVD-2020-0326

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

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

Patch / fix

  • npm dojox 1.11.10, 1.12.8, 1.13.7, 1.14.6, 1.15.3, 1.16.2
  • linuxfoundation dojox 1.11.10, 1.12.8, 1.13.7, 1.14.6, 1.15.3, 1.16.2
  • dojo Debian 14, Debian 13, Debian 12 1.15.3+dfsg1-1

debian advisories DEBIAN-CVE-2020-5259

Exploit prediction

2.02% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/dojo/dojox/security/advisories/GHSA-3hw5-q855-g6cw referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
NVD 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 7.7 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm dojox
<1.11.10
>=1.12.0, <1.12.8
>=1.13.0, <1.13.7
>=1.14.0, <1.14.6
>=1.15.0, <1.15.3
>=1.16.0, <1.16.2
1.11.10
1.12.8
1.13.7
1.14.6
1.15.3
1.16.2

Affected products

  • dojo dojox

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.