Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

VBScript Content Injection in marked

CVE-2015-1370GHSA-cfjh-p3g4-3q2f

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (marked 0.3.3), 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

  • npm marked

    Affected
    < 0.3.3
    Fixed in
    0.3.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2015-1370: 2.04% estimated exploitation activity in the next 30 days; percentile 81.18 (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.

Versions 0.3.2 and earlier of marked are affected by a cross-site scripting vulnerability even when sanitize:true is set. Proof of Concept ( IE10 Compatibility Mode Only ) xss link will get a link <a href="vbscript:alert(1)"xss link</a Recommendation Update to version 0.3.3 or later.

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

    Amended from ghsa record GHSA-cfjh-p3g4-3q2f

  2. Revision 1 · created ·

    Published from osv record GHSA-cfjh-p3g4-3q2f

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-2015-1370

Advisory: VBScript Content Injection in marked
IDs: CVE-2015-1370, GHSA-cfjh-p3g4-3q2f
Record: https://patchnext.com/advisories/cve-2015-1370 (revision 2, source checked 26 Oct 2026, 12:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: marked 0.3.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm marked: affected < 0.3.3; fixed in 0.3.3

## Suggested inspection (read-only)
- `npm ls marked --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 marked.
- 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-cfjh-p3g4-3q2f (OSV record GHSA-cfjh-p3g4-3q2f lists affected ranges: npm marked >=0 <0.3.3 (fixed))
- Verified: https://github.com/advisories/GHSA-cfjh-p3g4-3q2f (GitHub-reviewed advisory GHSA-cfjh-p3g4-3q2f lists affected ranges: npm marked >=0 <0.3.3)

Commands are suggestions: review each one before running it.

Loading voting…