KeystoneJS before 4.0.0-beta.7 allows application-wide CSRF bypass by removing the CSRF parameter and value, aka SecureLayer7 issue number SL7_KEYJS_03. In other words, it fails to reject requests that lack an x-csrf-token header.
Loading...
Loading...
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 58% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
KeystoneJS before 4.0.0-beta.7 allows application-wide CSRF bypass by removing the CSRF parameter and value, aka SecureLayer7 issue number SL7_KEYJS_03. In other words, it fails to reject requests that lack an x-csrf-token header.
November 6, 2017
May 13, 2026
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| keystone | — | 4.0.0-beta.7 | — |
Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.
Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
KeystoneJS < 4.0.0-beta.7 - Cross-Site Request Forgery
Open source ↗See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-16570
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.