VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

send: vulnerability history, versions and safety

send is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 60 releases, from Oct 2017 to Sep 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M2 L2
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 send vulnerabilities

Vulert verdict on send 1.2.1 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 1.2.1 — unaffected i
  • Vulnerabilities on record 4 over 6 years · 0 in the last year i
  • Latest disclosure 10 Sep 2024 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 121,788 packages i
  • Stars 812 i
  • OpenSSF scorecard 5/10 i
  • Last release 10 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 send, 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.2.1 15 Dec 2025 none MIT — Details →
0.19.2 15 Dec 2025 none MIT — Details →
1.2.0 27 Mar 2025 none MIT — Details →
0.19.1 09 Oct 2024 none MIT — Details →
1.1.0 10 Sep 2024 none MIT — Details →
0.19.0 10 Sep 2024 none MIT — Details →
1.0.0 25 Jul 2024 none MIT — Details →
1.0.0-beta.2 21 Mar 2024 none MIT — Details →
0.18.0 24 Mar 2022 L1 MIT Yes Details →
1.0.0-beta.1 05 Feb 2022 none MIT — Details →
0.17.2 12 Dec 2021 L1 MIT Yes Details →
0.17.1 11 May 2019 L1 MIT Yes Details →
0.17.0 03 May 2019 L1 MIT Yes Details →
0.16.2 07 Feb 2018 L1 MIT Yes Details →
0.16.1 29 Sep 2017 L1 MIT Yes Details →
0.16.0 28 Sep 2017 L1 MIT Yes Details →
0.15.6 22 Sep 2017 L1 MIT Yes Details →
0.15.5 21 Sep 2017 L1 MIT Yes Details →
0.15.4 06 Aug 2017 L1 MIT Yes Details →
0.15.3 17 May 2017 L1 MIT Yes Details →
0.15.2 26 Apr 2017 L1 MIT Yes Details →
0.15.1 05 Mar 2017 L1 MIT Yes Details →
0.15.0 25 Feb 2017 L1 MIT Yes Details →
0.14.2 23 Jan 2017 L1 MIT Yes Details →
0.14.1 10 Jun 2016 L1 MIT Yes Details →
0.14.0 07 Jun 2016 L1 MIT Yes Details →
0.13.2 06 Mar 2016 L1 MIT Yes Details →
0.13.1 16 Jan 2016 L1 MIT Yes Details →
0.13.0 17 Jun 2015 L1 MIT Yes Details →
0.12.3 13 May 2015 L1 MIT Yes Details →
0.12.2 14 Mar 2015 L1 MIT Yes Details →
0.12.1 17 Feb 2015 L1 MIT Yes Details →
0.12.0 16 Feb 2015 L1 MIT Yes Details →
0.11.1 20 Jan 2015 L1 MIT Yes Details →
0.11.0 05 Jan 2015 M1 L1 MIT Yes Details →
0.10.1 23 Oct 2014 M1 L1 MIT Yes Details →
0.10.0 16 Oct 2014 M1 L1 MIT Yes Details →
0.9.3 24 Sep 2014 M1 L1 MIT Yes Details →
0.9.2 16 Sep 2014 M1 L1 MIT Yes Details →
0.9.1 08 Sep 2014 M1 L1 MIT Yes Details →
0.9.0 08 Sep 2014 M1 L1 MIT Yes Details →
0.8.5 05 Sep 2014 M1 L1 MIT Yes Details →
0.8.4 04 Sep 2014 M1 L1 MIT Yes Details →
0.8.3 17 Aug 2014 M2 L2 MIT Yes Details →
0.8.2 15 Aug 2014 M2 L2 MIT Yes Details →
0.8.1 06 Aug 2014 M2 L2 MIT Yes Details →
0.8.0 06 Aug 2014 M2 L2 MIT Yes Details →
0.7.4 04 Aug 2014 M2 L2 MIT Yes Details →
0.7.3 30 Jul 2014 M2 L2 MIT Yes Details →
0.7.2 27 Jul 2014 M2 L2 MIT Yes Details →
0.7.1 26 Jul 2014 M2 L2 MIT Yes Details →
0.7.0 21 Jul 2014 M2 L2 MIT Yes Details →
0.6.0 12 Jul 2014 M2 L2 MIT Yes Details →
0.5.0 28 Jun 2014 M2 L2 MIT Yes Details →
0.4.3 12 Jun 2014 M2 L2 MIT Yes Details →
0.4.2 09 Jun 2014 M2 L2 MIT Yes Details →
0.4.1 02 Jun 2014 M2 L2 MIT Yes Details →
0.4.0 28 May 2014 M2 L2 MIT Yes Details →
0.3.0 24 Apr 2014 M2 L2 MIT Yes Details →
0.2.0 29 Jan 2014 M2 L2 MIT Yes Details →
0.1.4 10 Aug 2013 M2 L2 MIT Yes Details →
0.1.3 08 Jul 2013 M2 L2 MIT Yes Details →
0.1.2 03 Jul 2013 M2 L2 MIT Yes Details →
0.1.1 03 Jun 2013 M2 L2 MIT Yes Details →
0.1.0 19 Sep 2012 M2 L2 MIT Yes Details →
0.0.4 16 Aug 2012 M2 L2 MIT Yes Details →
0.0.3 16 Jul 2012 M2 L2 MIT Yes Details →
0.0.2 09 Jul 2012 M2 L2 MIT Yes Details →
0.0.1 04 Jul 2012 M2 L2 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2018 1
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for send

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-8859: Root Path Disclosure in send 5.3 medium 0.11.1 24 Oct 2017
CVE-2024-43799: Template Injection XSS in send package 5.0 low 0.19.0 10 Sep 2024
CVE-2014-6394: Directory Traversal in send N/A low 0.8.4 24 Oct 2017
Vulnerability in send package: Directory Traversal N/A medium 0.8.4 09 Oct 2018

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 send

Is send safe to use?

Vulert records 4 vulnerabilities for send in npm: 0 critical, 0 high, 2 medium and 2 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 send's Vulert package health score?

Vulert scores send 84/100, which reads as in good shape. 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 send affected?

No. 1.2.1, 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 send should I use?

1.2.1 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 send have?

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

How often are new send vulnerabilities disclosed?

0 vulnerabilities were recorded for send in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 send 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 send for upcoming vulnerabilities?

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