Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.3amended

@jmondi/url-to-png enables capture screenshot of localhost web services (unauthenticated pages)

CVE-2024-39919GHSA-342q-2mc2-5gmp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@jmondi/url-to-png 2.1.2), redeploy, then verify what is actually installed.

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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N · score source
EPSS
  • CVE-2024-39919: 0.37% estimated exploitation activity in the next 30 days; percentile 31.36 (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.

Summary The maintainer been contemplating whether FTP or other protocols could serve as useful functionalities, but there may not be a practical reason for it since we are utilizing headless Chrome to capture screenshots. The argument is based on the assumption that this package can function as a service. The package includes an ALLOWLIST where the host can specify which services the user is permitted to capture screenshots of. By default, capturing screenshots of web services running on localhost, 127.0.0.1, or the [::] is allowed. The maintainer is of the opinion that the package should also have a blacklist due to a potential vulnerability (or rather design oversight). If someone hosts this on a server, users could then capture screenshots of other web services running locally. Unless this is strictly for web pages. Something similar here: https://github.com/follow-redirects/follow-redirects/issues/235 (localhost is intended for end users or hosts to deny, and the package is for…

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

    Amended from ghsa record GHSA-342q-2mc2-5gmp

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-342q-2mc2-5gmp

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-2024-39919

Advisory: @jmondi/url-to-png enables capture screenshot of localhost web services (unauthenticated pages)
IDs: CVE-2024-39919, GHSA-342q-2mc2-5gmp
Record: https://patchnext.com/advisories/cve-2024-39919 (revision 3, source checked 26 Oct 2026, 12:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @jmondi/url-to-png 2.1.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @jmondi/url-to-png: affected < 2.1.2; fixed in 2.1.2

## Suggested inspection (read-only)
- `npm ls @jmondi/url-to-png --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @jmondi/url-to-png.
- 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-342q-2mc2-5gmp (OSV record GHSA-342q-2mc2-5gmp lists affected ranges: npm @jmondi/url-to-png >=0 <2.1.2 (fixed))
- Verified: https://github.com/advisories/GHSA-342q-2mc2-5gmp (GitHub-reviewed advisory GHSA-342q-2mc2-5gmp lists affected ranges: npm @jmondi/url-to-png >=0 <2.1.2)

Commands are suggestions: review each one before running it.

Loading voting…