Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Cross-Site Scripting in seeftl

CVE-2019-15603GHSA-4g46-5grc-wq49

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 seeftl

    Affected
    <= 0.1.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2019-15603: 0.75% estimated exploitation activity in the next 30 days; percentile 55.09 (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 seeftl are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code. Recommendation 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-4g46-5grc-wq49

  2. Revision 1 · created ·

    Published from osv record GHSA-4g46-5grc-wq49

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-2019-15603

Advisory: Cross-Site Scripting in seeftl
IDs: CVE-2019-15603, GHSA-4g46-5grc-wq49
Record: https://patchnext.com/advisories/cve-2019-15603 (revision 2, source checked 26 Oct 2026, 12:06 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 response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm seeftl: affected <= 0.1.1

## Suggested inspection (read-only)
- `npm ls seeftl --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 seeftl.
- 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-4g46-5grc-wq49 (OSV record GHSA-4g46-5grc-wq49 lists affected ranges: npm seeftl >=0 <=0.1.1)
- Verified: https://github.com/advisories/GHSA-4g46-5grc-wq49 (GitHub-reviewed advisory GHSA-4g46-5grc-wq49 lists affected ranges: npm seeftl >=0 <=0.1.1)

Commands are suggestions: review each one before running it.

Loading voting…