Laravel Sensitive Data Exposure

published 2017-09-27 9 y ago modified 2026-06-17 4 mo ago also GHSA-c2v7-j5gq-wcq4 , EUVD-2022-3480

cvss: 5.9; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.2%; EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits: 0; none known

Laravel before 5.5.10 mishandles the remember_me token verification process because DatabaseUserProvider does not have constant-time token comparison.

Patch / fix

fixed in 2 links 2

packagist laravel/framework 5.5.10
packagist illuminate/auth 5.5.10

github.com/laravel/framework#21320 pull request
github.com/laravel/framework/releases/tag/v5.5.10 release

Exploit prediction

1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.9	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub	3.0	5.9	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	laravel/framework	<5.5.10	5.5.10
packagist	illuminate/auth	<5.5.10	5.5.10

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

github.com /laravel/framework/pull/21320
web, issue-tracking, mailing-list, third-party-advisory
laravel-news.com /laravel-v5-5-11
web, issue-tracking, vendor-advisory
github.com /laravel/framework/releases/tag/v5.5.10
web, release-notes, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2017-14775
advisory
github.com /FriendsOfPHP/security-advisories/blob/master/illuminate/auth/CVE-2017-14775.yaml
web
github.com /FriendsOfPHP/security-advisories/blob/master/laravel/framework/CVE-2017-14775.yaml
web

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary