Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

@jmondi/url-to-png contains a Path Traversal vulnerability

CVE-2024-39918GHSA-vvmv-wrvp-9gjr

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.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2024-39918: 0.53% estimated exploitation activity in the next 30 days; percentile 44.73 (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 When trying to add a BLOCKLIST feature when the maintainer noticed they didn't sanitize the ImageId in the code, which leads to path traversal vulnerability. Now, this is different from a traditional path traversal issue, because as of NOW you can store the image in any place arbitrarily, and given enough time they might be able to come up with a working exploit BUT for the time being they am reporting this. Details @jmondi/url-to-png does not sanitizing the ImageID as in not removing special chars from the params (extractqueryparams.ts#l75) This when fed to other parts of the code such as (filesystem.ts#L34) Would result in path traversal issue. PoC Set this in your .env file and use this as your payload. This will create a .png file in the /tmp section of the system. Loom POC: https://www.loom.com/share/bd7b306cdae7445c97e68f0626e743a6 This is valid for pretty much all the arguments (except for numeric values) A simple fix would be to use the slugify for the params as well…

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

    Amended from ghsa record GHSA-vvmv-wrvp-9gjr

  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-vvmv-wrvp-9gjr

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-39918

Advisory: @jmondi/url-to-png contains a Path Traversal vulnerability
IDs: CVE-2024-39918, GHSA-vvmv-wrvp-9gjr
Record: https://patchnext.com/advisories/cve-2024-39918 (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.9)
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-vvmv-wrvp-9gjr (OSV record GHSA-vvmv-wrvp-9gjr lists affected ranges: npm @jmondi/url-to-png >=0 <2.1.2 (fixed))
- Verified: https://github.com/advisories/GHSA-vvmv-wrvp-9gjr (GitHub-reviewed advisory GHSA-vvmv-wrvp-9gjr lists affected ranges: npm @jmondi/url-to-png >=0 <2.1.2)

Commands are suggestions: review each one before running it.

Loading voting…