CVE-2018-15133
mediumpriority · act · 90OT risk · criticalKEV · exploitedEPSS 0.766 · 100 %ileexploit · weaponizedEUUSadded 2024-01-16remediate by 2024-02-06
required action Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
EPSS · scored 2026-10-27
Laravel Deserialization of Untrusted Data Vulnerability
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.8–8.1
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
exploits (14)
Public proof-of-concept and weaponised exploit code.
- AlienX2001/better-poc-for-CVE-2018-15133An automated PoC for CVE 2018-15133PoC · poc_in_github
- AzhariKun/CVE-2018-15133AzhariKun/CVE-2018-15133PoC · poc_in_github
- Loaxert/CVE-2018-15133-PoCLoaxert/CVE-2018-15133-PoCPoC · poc_in_github
affected products (5)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-qvqm-h22r-4cp9Laravel Framework RCE Vulnerability2022-05-14ghsa · osvUS
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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (9)
External citations — patches, advisories, analysis.
- http://packetstormsecurity.com/files/153641/PHP-Laravel-Framework-Token-Unserialize-Remote-Command-Execution.htmlcnnvd
- https://laravel.com/docs/5.6/upgrade#upgrade-5.6.30cnnvd
- https://packetstormsecurity.com/files/153641/PHP-Laravel-Framework-Token-Unserialize-Remote-Command-Execution.htmlcnnvd
- https://www.exploit-db.com/exploits/47129cnnvd
- http://packetstormsecurity.com/files/153641/PHP-Laravel-Framework-Token-Unserialize-Remote-Command-Execution.htmlenisa_euvd
- https://laravel.com/docs/5.6/upgrade#upgrade-5.6.30enisa_euvd
- http://packetstormsecurity.com/files/153641/PHP-Laravel-Framework-Token-Unserialize-Remote-Command-Execution.htmlExploitThird Party AdvisoryVDB Entrynvd
- https://laravel.com/docs/5.6/upgrade#upgrade-5.6.30Vendor Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan