Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

Keystone is vulnerable to CSV injection

CVE-2017-15879GHSA-6494-v9fq-fgq2

What to do

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

    Affected
    <= 4.0.0-beta5
    Fixed in
    4.0.0-beta7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
  • CVE-2017-15879: 7.22% estimated exploitation activity in the next 30 days; percentile 94.33 (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.

CSV Injection (aka Excel Macro Injection or Formula Injection) exists in admin/server/api/download.js and lib/list/getCSVData.js in KeystoneJS before 4.0.0-beta.7 via a value that is mishandled in a CSV export.

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

    Amended from ghsa record GHSA-6494-v9fq-fgq2

  2. Revision 1 · created ·

    Published from osv record GHSA-6494-v9fq-fgq2

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

Advisory: Keystone is vulnerable to CSV injection
IDs: CVE-2017-15879, GHSA-6494-v9fq-fgq2
Record: https://patchnext.com/advisories/cve-2017-15879 (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: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: keystone 4.0.0-beta7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm keystone: affected <= 4.0.0-beta5; fixed in 4.0.0-beta7

## Suggested inspection (read-only)
- `npm ls keystone --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 keystone.
- 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-6494-v9fq-fgq2 (OSV record GHSA-6494-v9fq-fgq2 lists affected ranges: npm keystone >=0 <4.0.0-beta7 (fixed))
- Verified: https://github.com/advisories/GHSA-6494-v9fq-fgq2 (GitHub-reviewed advisory GHSA-6494-v9fq-fgq2 lists affected ranges: npm keystone >=0 <=4.0.0-beta5)

Commands are suggestions: review each one before running it.

Loading voting…