VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

dojo: vulnerability history, versions and safety

dojo is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 104 releases, from Sep 2019 to Jan 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H2 M3
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 dojo vulnerabilities

Vulert verdict on dojo 1.17.3 i

Updated on 22 Oct 2026

Careful: 1.17.3 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.17.3 — affected i
  • Vulnerabilities on record 5 over 2 years · 0 in the last year i
  • Latest disclosure 05 Jan 2022 i
  • Highest CVSS 7.7 i
  • With no published fix 1 i
  • Depended on by 39 packages i
  • Stars 1,593 i
  • OpenSSF scorecard 2/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 dojo, 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 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.17.2 20 Mar 2022 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.17.1 07 Mar 2022 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.17.0 20 Feb 2022 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.11.13 20 Feb 2022 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.12.11 20 Feb 2022 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.13.10 20 Feb 2022 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.14.9 20 Feb 2022 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.15.6 20 Feb 2022 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.16.5 20 Feb 2022 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.11.12 21 Mar 2021 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.12.10 21 Mar 2021 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.13.9 21 Mar 2021 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.14.8 21 Mar 2021 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.15.5 21 Mar 2021 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.16.4 21 Mar 2021 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.11.11 13 Jun 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.12.9 13 Jun 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.13.8 13 Jun 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.14.7 13 Jun 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.15.4 13 Jun 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.16.3 13 Jun 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.16.2 10 Mar 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.15.3 10 Mar 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.17.0-pre 10 Mar 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.14.6 10 Mar 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.13.7 10 Mar 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.12.8 10 Mar 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.11.10 10 Mar 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.16.1 12 Feb 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.15.2 12 Feb 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.14.5 12 Feb 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.13.6 12 Feb 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.12.7 12 Feb 2020 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.11.9 12 Feb 2020 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.16.0 29 Nov 2019 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.15.1 29 Nov 2019 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.14.4 29 Nov 2019 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.13.5 29 Nov 2019 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.12.6 29 Nov 2019 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.11.8 29 Nov 2019 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.11.7 16 Feb 2019 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.12.5 16 Feb 2019 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.13.4 16 Feb 2019 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.14.3 16 Feb 2019 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.15.0 16 Feb 2019 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.13.3 01 Oct 2018 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.14.2 01 Oct 2018 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.13.2 31 Aug 2018 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.14.1 30 Aug 2018 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.10.10 13 Aug 2018 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.11.6 13 Aug 2018 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.12.4 13 Aug 2018 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.13.1 13 Aug 2018 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.14.0 11 Aug 2018 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.14.0-pre 11 Aug 2018 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.10.9 26 Sep 2017 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.13.0 26 Sep 2017 M1 AFL-2.1 OR BSD-3-Clause Yes Details →
1.12.3 26 Sep 2017 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.11.5 26 Sep 2017 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.12.2 05 Mar 2017 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.11.4 05 Mar 2017 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.10.8 05 Mar 2017 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.9.11 05 Mar 2017 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.8.14 05 Mar 2017 H2 M1 AFL-2.1 OR BSD-3-Clause No Details →
1.7.12 05 Mar 2017 H2 M1 AFL-2.1 OR BSD-3-Clause No Details →
1.6.5 05 Mar 2017 H2 M1 AFL-2.1 OR BSD-3-Clause No Details →
1.12.1 20 Dec 2016 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.11.3 19 Dec 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.10.7 19 Dec 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.9.10 19 Dec 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.8.13 19 Dec 2016 H2 M1 AFL-2.1 OR BSD-3-Clause No Details →
1.7.11 19 Dec 2016 H2 M1 AFL-2.1 OR BSD-3-Clause No Details →
1.6.4 19 Dec 2016 H2 M1 AFL-2.1 OR BSD-3-Clause No Details →
1.9.9 10 Jun 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.10.6 10 Jun 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.11.2 10 Jun 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.11.1 01 Apr 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
2.0.0-alpha.7 01 Apr 2016 H1 BSD-3-Clause No Details →
1.9.7 21 Mar 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.9.6 21 Mar 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.11.0-rc5 21 Mar 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.9.8 21 Mar 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.10.5 21 Mar 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.11.0 21 Mar 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.11.0-rc4 08 Mar 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.11.0-rc3 27 Feb 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.11.0-rc1 22 Feb 2016 H2 AFL-2.1 OR BSD-3-Clause No Details →
2.0.0-alpha.6 05 Jun 2015 H1 BSD-3-Clause No Details →
2.0.0-alpha.5 22 Apr 2015 H1 BSD-3-Clause No Details →
1.10.4 16 Mar 2015 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.10.3 16 Mar 2015 H2 AFL-2.1 OR BSD-3-Clause No Details →
2.0.0-alpha4 05 Dec 2014 H1 AFL-2.1 OR BSD-3-Clause No Details →
2.0.0-alpha3 04 Dec 2014 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.9.5 20 Oct 2014 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.10.2 19 Oct 2014 H2 AFL-2.1 OR BSD-3-Clause No Details →
2.0.0-alpha2 13 Sep 2014 H1 AFL-2.1 OR BSD-3-Clause No Details →
1.10.1 12 Sep 2014 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.9.4 12 Sep 2014 H2 AFL-2.1 OR BSD-3-Clause No Details →
1.10.0 22 Jun 2014 H2 AFL-2.1 OR BSD-3-Clause No Details →
2.0.0-alpha1 22 Jun 2014 H1 — No Details →
1.9.3 26 Feb 2014 H2 — No Details →
1.9.2 06 Dec 2013 H2 — No Details →
1.9.1 05 Jul 2013 H2 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2020 3
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for dojo

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-5258: Prototype Pollution in dojo 7.7 high 1.11.10 10 Mar 2020
CVE-2021-23450: Prototype Pollution in dojo 7.5 high No fix published 05 Jan 2022
CVE-2015-5654: Cross-Site Scripting in dojo 5.4 medium 1.9.1 11 Sep 2020
CVE-2008-6681: Cross-Site Scripting in dojo N/A medium 1.1.0 01 Sep 2020
CVE-2010-2273: Cross-Site Scripting in dojo N/A medium 1.13.1 11 Sep 2019

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 dojo

Is dojo safe to use?

Vulert records 5 vulnerabilities for dojo in npm: 0 critical, 2 high, 3 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is dojo's Vulert package health score?

Vulert scores dojo 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of dojo affected?

Yes. 1.17.3, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of dojo 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 dojo have?

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

How often are new dojo vulnerabilities disclosed?

0 vulnerabilities were recorded for dojo in the last 12 months, and the oldest entry in this database dates to 11 Sep 2019. 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 dojo 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 dojo for upcoming vulnerabilities?

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