VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

dojox: vulnerability history, versions and safety

dojox is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 52 releases, from Oct 2018 to Mar 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 M1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all dojox vulnerabilities

Vulert verdict on dojox 1.17.3 i

Updated on 23 Oct 2026

Good news: 1.17.3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 53/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

What to do: Stay on 1.17.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.17.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.17.3 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 10 Mar 2020 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 152 i
  • OpenSSF scorecard 1/10 i
  • Last release 50 months ago i
  • Licence AFL-2.1 OR BSD-3-Clause i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for dojox, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.17.3 13 Aug 2022 none AFL-2.1 OR BSD-3-Clause — Details →
1.17.2 20 Mar 2022 none AFL-2.1 OR BSD-3-Clause — Details →
1.17.1 07 Mar 2022 none AFL-2.1 OR BSD-3-Clause — Details →
1.17.0 20 Feb 2022 none AFL-2.1 OR BSD-3-Clause — Details →
1.11.13 20 Feb 2022 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.11 20 Feb 2022 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.13.10 20 Feb 2022 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.14.9 20 Feb 2022 none AFL-2.1 OR BSD-3-Clause — Details →
1.15.6 20 Feb 2022 none AFL-2.1 OR BSD-3-Clause — Details →
1.16.5 20 Feb 2022 none AFL-2.1 OR BSD-3-Clause — Details →
1.11.12 21 Mar 2021 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.10 21 Mar 2021 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.13.9 21 Mar 2021 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.14.8 21 Mar 2021 none AFL-2.1 OR BSD-3-Clause — Details →
1.15.5 21 Mar 2021 none AFL-2.1 OR BSD-3-Clause — Details →
1.16.4 21 Mar 2021 none AFL-2.1 OR BSD-3-Clause — Details →
1.11.11 13 Jun 2020 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.9 13 Jun 2020 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.13.8 13 Jun 2020 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.14.7 13 Jun 2020 none AFL-2.1 OR BSD-3-Clause — Details →
1.15.4 13 Jun 2020 none AFL-2.1 OR BSD-3-Clause — Details →
1.16.3 13 Jun 2020 none AFL-2.1 OR BSD-3-Clause — Details →
1.16.2 10 Mar 2020 none AFL-2.1 OR BSD-3-Clause — Details →
1.15.3 10 Mar 2020 none AFL-2.1 OR BSD-3-Clause — Details →
1.14.6 10 Mar 2020 none AFL-2.1 OR BSD-3-Clause — Details →
1.13.7 10 Mar 2020 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.8 10 Mar 2020 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.10 10 Mar 2020 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.16.1 12 Feb 2020 none AFL-2.1 OR BSD-3-Clause — Details →
1.15.2 12 Feb 2020 none AFL-2.1 OR BSD-3-Clause — Details →
1.14.5 12 Feb 2020 none AFL-2.1 OR BSD-3-Clause — Details →
1.13.6 12 Feb 2020 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.7 12 Feb 2020 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.9 12 Feb 2020 C1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.16.0 29 Nov 2019 none AFL-2.1 OR BSD-3-Clause — Details →
1.15.1 29 Nov 2019 none AFL-2.1 OR BSD-3-Clause — Details →
1.14.4 29 Nov 2019 none AFL-2.1 OR BSD-3-Clause — Details →
1.13.5 29 Nov 2019 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.6 29 Nov 2019 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.8 29 Nov 2019 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.7 16 Feb 2019 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.5 16 Feb 2019 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.13.4 16 Feb 2019 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.14.3 16 Feb 2019 none AFL-2.1 OR BSD-3-Clause — Details →
1.15.0 16 Feb 2019 none AFL-2.1 OR BSD-3-Clause — Details →
1.13.3 01 Oct 2018 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.14.2 01 Oct 2018 none AFL-2.1 OR BSD-3-Clause — Details →
1.13.2 31 Aug 2018 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.14.1 30 Aug 2018 none AFL-2.1 OR BSD-3-Clause — Details →
1.10.10 13 Aug 2018 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.6 13 Aug 2018 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.4 13 Aug 2018 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.13.1 13 Aug 2018 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.14.0 11 Aug 2018 none AFL-2.1 OR BSD-3-Clause — Details →
1.13.0 26 Sep 2017 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.3 26 Sep 2017 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.5 26 Sep 2017 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.2 05 Mar 2017 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.4 05 Mar 2017 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.9.11 05 Mar 2017 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.8.14 05 Mar 2017 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.7.12 05 Mar 2017 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.6.5 05 Mar 2017 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.1 20 Dec 2016 C1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.3 19 Dec 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.9.10 19 Dec 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.8.13 19 Dec 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.7.11 19 Dec 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.6.4 19 Dec 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.9.9 10 Jun 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.2 10 Jun 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.1 01 Apr 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.0 21 Mar 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.0-rc4 08 Mar 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.0-rc3 04 Mar 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.0-rc2 04 Mar 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.11.0-rc1 04 Mar 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.9.7 04 Mar 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.10.3 04 Mar 2016 C1 M1 L1 AFL-2.1 OR BSD-3-Clause Yes Details →

All 79 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2020 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for dojox

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-15494: Critical vulnerability in dojox 9.8 critical 1.14.0 15 Oct 2018
CVE-2020-5259: Prototype Pollution in Dojox 7.7 low 1.11.10 10 Mar 2020
CVE-2019-10785: XSS Vulnerability in dojox.xmpp.util.xmlEncode 6.1 medium 1.11.9 13 Feb 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About dojox

Is dojox safe to use?

Vulert records 3 vulnerabilities for dojox in npm: 1 critical, 0 high, 1 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is dojox's Vulert package health score?

Vulert scores dojox 53/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of dojox affected?

No. 1.17.3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of dojox should I use?

1.17.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does dojox have?

3 vulnerabilities are recorded for dojox in the npm ecosystem: 1 critical, 0 high, 1 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new dojox vulnerabilities disclosed?

0 vulnerabilities were recorded for dojox in the last 12 months, and the oldest entry in this database dates to 15 Oct 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of dojox are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor dojox for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the dojox version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.