Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.8amended

File restriction bypass in socket.io-file

CVE-2020-24807GHSA-6495-8jvh-f28x

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm socket.io-file

    Affected
    <= 2.0.31
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.8 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
  • CVE-2020-24807: 2.10% estimated exploitation activity in the next 30 days; percentile 81.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

All versions of socket.io-fileare vulnerable to a file restriction bypass. The validation for valid file types only happens on the client-side, which allows an attacker to intercept the Websocket request post-validation and alter the name value to upload any file types. No fix is currently available. Consider using an alternative package until a fix is made available.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-6495-8jvh-f28x

  2. Revision 1 · created ·

    Published from osv record GHSA-6495-8jvh-f28x

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-24807

Advisory: File restriction bypass in socket.io-file
IDs: CVE-2020-24807, GHSA-6495-8jvh-f28x
Record: https://patchnext.com/advisories/cve-2020-24807 (revision 2, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm socket.io-file: affected <= 2.0.31

## Suggested inspection (read-only)
- `npm ls socket.io-file --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on socket.io-file.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6495-8jvh-f28x (OSV record GHSA-6495-8jvh-f28x lists affected ranges: npm socket.io-file >=0 <=2.0.31)
- Verified: https://github.com/advisories/GHSA-6495-8jvh-f28x (GitHub-reviewed advisory GHSA-6495-8jvh-f28x lists affected ranges: npm socket.io-file >=0 <=2.0.31)

Commands are suggestions: review each one before running it.

Loading voting…