CVE-2018-15133
HighExploitedPublic exploitLaravel Framework RCE Vulnerability
Published May 14, 2022 · Updated Jul 8, 2026 · Also known as GHSA-qvqm-h22r-4cp9
Key Facts
Patch immediately- CVE-2018-15133 is a high-severity vulnerability (CVSS 8.1 v3.1) affecting Laravel, laravel/framework (composer), php-laravel-framework (debian).
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Mar 17, 2023. Public exploit code is available.
- EPSS estimates a 77% probability of exploitation in the next 30 days.
- Fixed versions are available, including Laravel <=5.5.40, laravel/framework 5.6.30, Laravel 5.5.40.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
8.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
77%
Higher than 99.5% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2018-15133 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Jan 16, 2024 | Feb 6, 2024 | Not reported |
| Industry KEV feed | Mar 17, 2023 | Feb 6, 2024 | Not reported |
| CIRCL KEV | Jan 16, 2024 | Feb 6, 2024 | Not reported |
| ENISA EUVD | Jan 16, 2024 | n/a | Not reported |
Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Affected Products
7 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| LaravelLaravel | See advisory | 5.5.40 |
| laravel/frameworkcomposer | >= 5.6.0 | 5.6.30 |
| php-laravel-frameworkdebian | See advisory | 0 |
Patched Releases
Laravel
<=5.5.40
laravel/framework
5.6.30
Timeline
Publicly disclosed
May 14, 2022
Added to Industry KEV feed
Mar 17, 2023
Added to CISA KEV
Jan 16, 2024
Added to CIRCL KEV
Jan 16, 2024
Added to ENISA EUVD
Jan 16, 2024
Last updated
Jul 8, 2026
Weakness Type
- CWE-502 Deserialization of Untrusted Data
References
- advisoryGHSA advisory
- advisoryhttps://github.com/kozmic/laravel-poc-CVE-2018-15133
- advisoryhttps://github.com/laravel/framework/commit/d84cf988ed5d4661a4bf1fdcb08f5073835083a0
- advisoryhttps://laravel.com/docs/5.6/upgrade#upgrade-5.6.30
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2018-15133
FAQ
Common Questions.
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.
Affected: Laravel; laravel/framework (composer) versions >= 5.6.0; php-laravel-framework (debian). The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Mar 17, 2023.
Yes. It was added on Jan 16, 2024 with a federal remediation due date of Feb 6, 2024.
Public exploit code is available.
Fixed versions are available, including Laravel <=5.5.40, laravel/framework 5.6.30, Laravel 5.5.40.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2018-15133 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo