Live › vulnerability › CVE-2018-15133
Go to dashboardLaravel Framework deserializes untrusted data in its cookie/encryption handling, allowing remote command execution. An attacker who already holds the application encryption key (APP_KEY) can send crafted serialized payloads to run commands on the server.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Laravel Laravel Framework | vendor | – | – |
| laravel | vendor | <= 5.5.40 | – |
| laravel | vendor | >= 5.6.0, <= 5.6.29 | – |
Check whether APP_KEY in the .env file or environment has ever been exposed; grep the framework version with composer show laravel/framework.
Upgrade laravel/framework to a release that includes the vendor fix, and rotate APP_KEY if it may have leaked.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In Laravel Framework through 5.5.40 and 5.6.x through 5.6.29, remote code execution might occur as a result of an unserialize call on a potentially untrusted X-XSRF-TOKEN value. This involves the decrypt method in Illuminate/Encryption/Encrypter.php and PendingBroadcast in gadgetchains/Laravel/RCE/3/chain.php in phpggc. The attacker must know the application key, which normally would never occur, but could happen if the attacker previously had privileged access or successfully accomplished a previous attack.
This page as .md · .json · in your agent: get_signal("CVE-2018-15133")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.