Laravel before 5.5.10 mishandles the remember_me token verification process because DatabaseUserProvider does not have constant-time token comparison.
Loading...
Loading...
This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 48% 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).
Laravel before 5.5.10 mishandles the remember_me token verification process because DatabaseUserProvider does not have constant-time token comparison.
September 28, 2017
May 13, 2026
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| illuminate/auth | v1.0.0 ... v5.5.2 (108 versions) | 5.5.10 | — |
| laravel/framework | 5.0.30 ... v5.5.9 (281 versions) | 5.5.10 | — |
Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-14775
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.