Vulnerability Database · npm · socket.io-file · Version

socket.io-file 2.0.13

2.0.13 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: 2.0.31.

Critical 0 High 3 Medium 0 Low 0 Unrated 0

Released 19 Jan 2017 Licence MIT Also known from other sources 2 Newer releases 30 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

socket.io-file 2.0.13 vulnerabilities

3 vulnerabilities cover socket.io-file 2.0.13. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2020-24807: Arbitrary code execution in socket.io-file 7.8 high No fix published 10 May 2021
File restriction bypass in socket.io-file 7.8 high No fix published 02 Oct 2020
Path Traversal in socket.io-file 7.5 high No fix published 07 Jul 2020

Looking for another version, or everything Vulert holds for socket.io-file?

All versions → Full vulnerability list →

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 socket.io-file 2.0.13

Is socket.io-file 2.0.13 vulnerable?

Yes. 3 vulnerabilities in the Vulert database cover socket.io-file 2.0.13: 0 critical, 3 high, 0 medium and 0 low. The upgrade Vulert recommends is 2.0.31, and each entry above names the fixed version to move to.

Which version of socket.io-file should I use instead of 2.0.13?

2.0.31 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.0.13 the latest release of socket.io-file?

No. 2.0.13 was published 19 Jan 2017, 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 socket.io-file for upcoming vulnerabilities?

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