Skip to content
Server Security Center
KEVhigh8.1

CVE-2018-15133: Laravel Deserialization of Untrusted Data

Laravel Framework · listed in the CISA catalog of actively exploited vulnerabilities since 2024-01-16.

CVSS v3.1 (CISA ADP)
8.1
high
EPSS (exploit probability, 30 days)
77%
higher than 99.5% of all CVEs
Added to CISA KEV
2024-01-16
US federal due date 2024-02-06
Automatable (CISA SSVC)
no
technical impact: total

CVE-2018-15133 explained

CVE-2018-15133 is a deserialization of untrusted data flaw in Laravel Framework. The decrypt method in Illuminate/Encryption/Encrypter.php can unserialize a potentially untrusted X-XSRF-TOKEN value, which might lead to remote code execution. CISA lists it as known to be exploited, so affected applications deserve prompt attention.

Impact

An attacker who knows the application key can send a crafted X-XSRF-TOKEN value over the network and may execute code on the server. No privileges or user interaction are needed, but obtaining the key is the hard part. That normally requires earlier privileged access or a previous successful attack. CISA rates the technical impact as total and the attack as not automatable. Confidentiality, integrity and availability are all at high risk.

Who is affected

The description names Laravel Framework through 5.5.40 and 5.6.x through 5.6.29. However, the structured CVE record lists no affected versions, and it names no fixed version. Check the vendor advisory to confirm which releases contain the fix.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: laravel.com/docs/5.6/upgrade
  • CISA's deadline for US federal agencies: 2024-02-06 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Check which Laravel Framework version each application runs, and treat 5.5.40 and earlier and 5.6.x through 5.6.29 as affected.
  2. Upgrade to a Laravel Framework release that the vendor advisory confirms contains the fix.
  3. Rotate the application key if it may have been exposed through earlier access, leaks or a past compromise.
  4. Protect the application key: keep it out of source repositories, backups and logs that others can reach.
  5. Review servers for signs of compromise, because CISA lists this vulnerability as known to be exploited.

The CVE record names no fixed version. Follow the Laravel vendor advisory to find a release with the fix. CISA's required action is to apply mitigations per vendor instructions, or to discontinue use of the product if mitigations are unavailable. Until you can upgrade, rotate the application key, restrict who can access it and monitor for compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-502 Deserialization of Untrusted Data

Questions about CVE-2018-15133

Can any remote attacker exploit this?
Not easily. The attacker must know the application key. According to the description, that normally does not happen unless the attacker previously had privileged access or succeeded in an earlier attack. If the key is known, no login or user interaction is needed.
Is this vulnerability being exploited?
Yes. CISA added CVE-2018-15133 to its Known Exploited Vulnerabilities catalog on 2024-01-16, with a US federal due date of 2024-02-06. Whether ransomware campaigns use it is unknown.
Should we change the application key?
If there is any chance the key was exposed, rotating it is sensible. Exploitation depends on knowing the key, so a new, protected key reduces the risk while you upgrade.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.