Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.3amended

GitHub Security Lab (GHSL) Vulnerability Report, scrypted: GHSL-2023-218, GHSL-2023-219

GHSA-w4hv-vmv9-hgcr

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 @scrypted/server

    Affected
    <= 0.56.0
    Fixed in
    no fixed version recorded

  • npm @scrypted/core

    Affected
    <= 0.1.142
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

GitHub Security Lab (GHSL) Vulnerability Report, scrypted: GHSL-2023-218, GHSL-2023-219 The GitHub Security Lab team has identified potential security vulnerabilities in scrypted. We are committed to working with you to help resolve these issues. In this report you will find everything you need to effectively coordinate a resolution of these issues with the GHSL team. If at any point you have concerns or questions about this process, please do not hesitate to reach out to us at securitylab@github.com (please include GHSL-2023-218 or GHSL-2023-219 as a reference). See also this blog post written by GitHub's Advisory Curation team which explains what CVEs and advisories are, why they are important to track vulnerabilities and keep downstream users informed, the CVE assigning process, and how they are used to keep open source software secure. If you are NOT the correct point of contact for this report, please let us know! Summary Two refelcted Cross-Site Scripting (XSS) vulnerabilities…

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

    Amended from ghsa record GHSA-w4hv-vmv9-hgcr

  2. Revision 1 · created ·

    Published from osv record GHSA-w4hv-vmv9-hgcr

Agent brief

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

# Patch Next advisory brief: GHSA-w4hv-vmv9-hgcr

Advisory: GitHub Security Lab (GHSL) Vulnerability Report, scrypted: `GHSL-2023-218`, `GHSL-2023-219`
IDs: GHSA-w4hv-vmv9-hgcr
Record: https://patchnext.com/advisories/ghsa-w4hv-vmv9-hgcr (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
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 @scrypted/server: affected <= 0.56.0
- npm @scrypted/core: affected <= 0.1.142

## Suggested inspection (read-only)
- `npm ls @scrypted/server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @scrypted/core --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 @scrypted/server, @scrypted/core.
- 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-w4hv-vmv9-hgcr (OSV record GHSA-w4hv-vmv9-hgcr lists affected ranges: npm @scrypted/server >=0 =0 <=0.1.142)
- Verified: https://github.com/advisories/GHSA-w4hv-vmv9-hgcr (GitHub-reviewed advisory GHSA-w4hv-vmv9-hgcr lists affected ranges: npm @scrypted/server >=0 =0 <=0.1.142)

Commands are suggestions: review each one before running it.

Loading voting…