Vulnerability Database · npm · send · Version
send 0.0.1
0.0.1 is affected by 4 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.2.1.
Critical 0 High 0 Medium 2 Low 2 Unrated 0
-
Released 04 Jul 2012
Licence MIT
Also known from other sources 3
Newer releases 69
Database updated 23/Oct/2026
Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version
send 0.0.1 vulnerabilities
4 vulnerabilities cover send 0.0.1. Open the full list 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 |
| Vulnerability in send package: Directory Traversal | N/A medium | 0.8.4 | 09 Oct 2018 |
| CVE-2014-6394: Directory Traversal in send | N/A low | 0.8.4 | 24 Oct 2017 |
Looking for another version, or everything Vulert holds for send?
Questions
About send 0.0.1
Is send 0.0.1 vulnerable?
Yes. 4 vulnerabilities in the Vulert database cover send 0.0.1: 0 critical, 0 high, 2 medium and 2 low. The upgrade Vulert recommends is 1.2.1, and each entry above names the fixed version to move to.
Which version of send should I use instead of 0.0.1?
1.2.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.0.1 the latest release of send?
No. 0.0.1 was published 04 Jul 2012, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.