Path Traversal in socket.io-file

published 2020-07-07 6y ago modified 2026-06-17 4mo ago also GHSA-9h4g-27m8-qjrg , EUVD-2020-0547

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.6%; EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits: 0; none known

A Path Traversal issue was discovered in the socket.io-file package through 2.0.31 for Node.js. The socket.io-file::createFile message uses path.join with ../ in the name option, and the uploadDir and rename options determine the path.

Is CVE-2020-15779 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.58% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

npmjs.com https://www.npmjs.com/advisories/1519 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	socket.io-file	<=2.0.31	no fix listed

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

npmjs.com /advisories/1519
web, exploit, third-party-advisory
npmjs.com /package/socket.io-file
web, product, third-party-advisory
github.com /rico345100/socket.io-file
package, third-party-advisory
github.com /advisories/GHSA-9h4g-27m8-qjrg
advisory, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2020-15779
advisory

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.