Skip to content
Fencer Intel
critical 9.8

CVE-2018-15494 json

dojox vulnerable to unescaped string injection

published 8y ago modified 4mo ago also GHSA-84cm-x2q5-8225 , EUVD-2018-0543

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

In Dojo Toolkit before 1.14, there is unescaped string injection in dojox/Grid/DataGrid.

Patch / fix

  • npm dojox 1.14.0
  • dojotoolkit dojo 1.14
  • dojo Debian 14, Debian 13, Debian 12 1.14.1+dfsg1-1

debian advisories DEBIAN-CVE-2018-15494

  • dojo Ubuntu Pro 16.04 LTS 1.10.4+dfsg-2ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2018-15494

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2018-15494 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-15494 updated cvss 6.1

dojo: Cross-site scripting (XSS) due to unescaped strings when editing rows in dojox/Grid/DataGrid

  • Red Hat Satellite 5 dojo
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm dojox
<1.14.0
1.14.0

Classification

Weakness
  • CWE-116 Improper Encoding or Escaping of Output

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.