# Laravel Encrypter Component Potential Decryption Failure Leading to Unintended Behavior

Advisory record · `GHSA-7852-w36x-6mf6`

- **Identifiers:** `GHSA-7852-w36x-6mf6`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-1240](https://cwe.mitre.org/data/definitions/1240.html)
- **Tags:** [CWE-1240](https://agentprime.io/advisories/tag/cwe-1240.md)
- **Published:** 15 May 2024
- **Updated:** 29 Nov 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 May 2024, 22:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `laravel/framework` (Packagist): affected `<5.5.40 || >=5.6.0, <5.6.15`; fixed in `5.5.40`, `5.6.15`

## Machine-written summary

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

> Laravel's laravel/framework package, versions before 5.5.40 and from 5.6.0 before 5.6.15, has an Encrypter component that can return false instead of raising an error when decryption fails. An attacker who can modify an encrypted payload before it is decrypted can trigger this, and the impact depends on whether the application compares the result loosely. Upgrade to 5.5.40 or 5.6.15 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

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 15 May 2024. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-7852-w36x-6mf6](https://github.com/advisories/GHSA-7852-w36x-6mf6)
- [OSV: GHSA-7852-w36x-6mf6](https://osv.dev/vulnerability/GHSA-7852-w36x-6mf6)
- <https://github.com/laravel/framework/commit/28e53f23a76206fb130e9a54eb95aa3f010e79c9>
- <https://github.com/laravel/framework/commit/886d261df0854426b4662b7ed5db6a1c575a4279>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/laravel/framework/2018-03-30-1.yaml>
- <https://github.com/laravel/framework>
- <https://medium.com/@taylorotwell/laravel-security-release-5-6-15-and-5-5-40-56f1257933a0>

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-7852-w36x-6mf6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7852-w36x-6mf6/>. Everything for agents: <https://agentprime.io/llms.txt>.