llamaCVEVulnerability Intelligence
/
Laravel Framework

CVE-2018-15133

Laravel Framework remote code execution in XSRF TOKEN handling

An attacker with the app's encryption key could run arbitrary code on the server via a crafted X-XSRF-TOKEN header.

CISA KEV · explotación activaCrítica · en CISA KEV, EPSS ≥ 10 %Parche disponible
Descargar PNG JSON
CVSS 3.1
8.1
Alta
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Fuente: NVD
ExplotaciónActivaEn CISA KEV desde 16 ene 2024
Exploits públicos0Explotada, pero sin código público enlazado
Parche1 versión5.6.30
Exposición3.025 dDesde la divulgación, 9 ago 2018, 2:00 p. m.
EPSS ≥ 10 %22 oct 2026Fecha en que la probabilidad de explotación superó el umbral
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
CISA KEV
Umbral EPSS
Remediación
Plazo KEV
Monitoreo
Detectada
Verificada
9 ago 18
16 ene 24
6 feb 24
21 oct 25
22 oct 26
12 nov 26
21 nov 26
9 ago 18
4 sept 20
30 sept 22
25 oct 24
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2018-15133 divulgada · CVSS 8.1 (NVD)
Explotación CISA KEV Agregada al catálogo de vulnerabilidades explotadas
Remediación Plazo KEV Fecha límite de remediación para agencias federales (EE. UU.)
Divulgación Modificada Última actualización del registro
Explotación Umbral EPSS La probabilidad de explotación supera el 10 %
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 11 nov 2026

Laravel Framework (the laravel/framework package) can let an attacker run code on the server by sending a crafted cookie value that the application unserializes. It can be reached remotely without logging in, but only if the attacker already holds the application's encryption key, and attacks using it are happening.

Affects laravel/framework through 5.5.40 and 5.6.x before 5.6.30, and only if the APP_KEY has been accessed by a malicious party and cookie serialization is on. Fixed in 5.6.30.

¿Qué significa?Laravel unserializes decrypted cookie values. Someone holding the application's encryption key (APP_KEY) could craft cookie values that abuse PHP unserialization to call arbitrary class methods, which can lead to remote code execution.
¿Quién está afectado?Laravel framework versions through 5.5.40 and 5.6.0 up to (not including) 5.6.30 are listed. Exposure also requires encrypted cookie serialization to be enabled (or re-enabled via the serialize property) and the APP_KEY to have been accessed by a malicious party. The installed version can be checked in composer.lock or with the laravel/framework package version, and the APP_KEY in the environment settings.
¿Qué hacer?Laravel calls 5.6.30 a security release and recommends an immediate upgrade. If the encryption key may be in the hands of a malicious party, rotate the application encryption key to a new value.
Descripción original del registro

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.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Application encryption key (APP_KEY) must have been accessed by a malicious party“This vulnerability may only be exploited if your application encryption key ( APP_KEY environment variable) has been accessed by a malicious user.”
02
Application uses encrypted cookie serialization (enabled in versions before 5.6.30, or re-enabled via the serialize property)“When encrypted cookie serialization is enabled, your application will be vulnerable to attack if its encryption key is accessed by a malicious party.”
¿Quién debe revisar?Teams running Laravel 5.6 before 5.6.30 (or 5.5 and earlier) whose APP_KEY may have leaked, e.g. to ex-employees; or who re-enabled encrypted cookie serialization.
No protegeRe-enabling cookie serialization after upgrading leaves the app vulnerable if the key is exposed; rotate the key first.
MitigaciónRotate the application encryption key to a new value if it may be in the hands of a malicious party.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · NVD
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
10.0/ 10Muy alto
Vector 7.1 (fácil) · +2.9 por explotación activa.
Versiones

Rangos afectados

Afectada Corregida
laravel/framework≤ 5.5.40
laravel/framework≥ 5.6.0 < 5.6.30
5.5.40
5.6.0
5.6.30
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
laravel/framework
Corregida 5.6.30 — —
Versiones corregidas5.6.30
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Exploithttp://packetstormsecurity.com/files/153641/PHP-Laravel-Framework-Token-Unserialize-Remote-Command-Execution.html
Otrahttps://laravel.com/docs/5.6/upgrade#upgrade-5.6.30

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.