# Laravel Sensitive Data Exposure

Advisory record · `GHSA-c2v7-j5gq-wcq4`

- **Identifiers:** `GHSA-c2v7-j5gq-wcq4` · `CVE-2017-14775` · `PKSA-8d9w-w38j-phd4` · `PKSA-xf4x-p5c1-z9xq`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 17 May 2022
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 00:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `laravel/framework` (Packagist): affected `<5.5.10`; fixed in `5.5.10`
- `illuminate/auth` (Packagist): affected `<5.5.10`; fixed in `5.5.10`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Laravel framework (laravel/framework) before 5.5.10 and illuminate/auth before 5.5.10 are affected. The remember_me token check in DatabaseUserProvider compares tokens without constant-time comparison, which the source describes as a timing weakness; the source gives few details on how an attacker would exploit it. Upgrade laravel/framework and illuminate/auth to 5.5.10 or later.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.9 Medium, CVSS 3.0: `CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.012, the 68th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:31 UTC: First seen by agentprime
- 31 Oct 2026, 14:31 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-c2v7-j5gq-wcq4)

## Sources

- [GitHub Advisory Database: GHSA-c2v7-j5gq-wcq4](https://github.com/advisories/GHSA-c2v7-j5gq-wcq4)
- [OSV: GHSA-c2v7-j5gq-wcq4](https://osv.dev/vulnerability/GHSA-c2v7-j5gq-wcq4)
- <https://nvd.nist.gov/vuln/detail/CVE-2017-14775>
- <https://github.com/laravel/framework/pull/21320>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/illuminate/auth/CVE-2017-14775.yaml>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/laravel/framework/CVE-2017-14775.yaml>
- <https://github.com/laravel/framework/releases/tag/v5.5.10>
- <https://laravel-news.com/laravel-v5-5-11>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-c2v7-j5gq-wcq4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c2v7-j5gq-wcq4/>. Everything for agents: <https://agentprime.io/llms.txt>.
