Vulnerability Database · npm · connect · Version
connect 2.8.0
2.8.0 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 3.7.0.
Critical 0 High 0 Medium 2 Low 1 Unrated 0
-
Released 26 Jun 2013
Status deprecated release
Licence MIT
Also known from other sources 0
Newer releases 234
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
connect 2.8.0 vulnerabilities
3 vulnerabilities cover connect 2.8.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2013-7371: Node Connect Reflected Cross-Site Scripting in Sencha Labs Connect middleware | 6.1 medium | 2.8.2 | 05 May 2022 |
| CVE-2018-3717: Cross-Site Scripting in connect | 5.4 medium | 2.14.0 | 26 Jul 2018 |
| CVE-2013-7370: methodOverride Middleware Reflected Cross-Site Scripting in connect | N/A low | 2.8.1 | 31 Aug 2020 |
Looking for another version, or everything Vulert holds for connect?
Questions
About connect 2.8.0
Is connect 2.8.0 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover connect 2.8.0: 0 critical, 0 high, 2 medium and 1 low. The upgrade Vulert recommends is 3.7.0, and each entry above names the fixed version to move to.
Which version of connect should I use instead of 2.8.0?
3.7.0 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 2.8.0 the latest release of connect?
No. 2.8.0 was published 26 Jun 2013, 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 connect for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the connect version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.