Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Cross-Site Scripting in morris.js

CVE-2017-16022GHSA-fwx5-5fqj-jv98

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 morris.js

    Affected
    >= 0.5.0, <= 0.5.0
    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-2017-16022: 0.89% estimated exploitation activity in the next 30 days; percentile 59.43 (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.

Affected versions of morris.js are vulnerable to cross-site scripting attacks in labels that appear when hovering over a particular point on a generated graph. The text content of these labels is not escaped, so if control over the labels is obtained, script can be injected. The script will run on the client side whenever that specific graph is loaded. Recommendation A patch for this vulnerability was created in 2014, but has still not been published to npm. In order to mitigate this issue effectively, install the library from github via:

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

    Amended from ghsa record GHSA-fwx5-5fqj-jv98

  2. Revision 1 · created ·

    Published from osv record GHSA-fwx5-5fqj-jv98

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-2017-16022

Advisory: Cross-Site Scripting in morris.js
IDs: CVE-2017-16022, GHSA-fwx5-5fqj-jv98
Record: https://patchnext.com/advisories/cve-2017-16022 (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 response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm morris.js: affected >= 0.5.0, <= 0.5.0

## Suggested inspection (read-only)
- `npm ls morris.js --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 morris.js.
- 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-fwx5-5fqj-jv98 (OSV record GHSA-fwx5-5fqj-jv98 lists affected ranges: npm morris.js >=0.5.0 <=0.5.0)
- Verified: https://github.com/advisories/GHSA-fwx5-5fqj-jv98 (GitHub-reviewed advisory GHSA-fwx5-5fqj-jv98 lists affected ranges: npm morris.js >=0.5.0 <=0.5.0)

Commands are suggestions: review each one before running it.

Loading voting…