Laravel MagicLink: Insecure Deserialization of MagicLink Actions Leads to Remote Code Execution
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| cesargb | laravel-magiclink | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Cesargb | Laravel-magiclink |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.762% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Cesargb
Cesargb laravel-magiclink |
|
| Vendors & Products |
Cesargb
Cesargb laravel-magiclink |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Laravel MagicLink creates links for authentication without a password or for accessing private content. From 2.0.0 until 2.25.1, MagicLink stores serialized action objects in the magic_links.action database column and deserializes them through src/MagicLink.php and src/Actions/ResponseAction.php without sufficient integrity protection, while an unsafe legacy unserialize() fallback remains reachable. An attacker who can manipulate database records, such as through a separate SQL injection or compromised administrative access, can insert a malicious serialized object graph containing executable closure behavior; visiting the associated magic link then deserializes the record and can execute arbitrary code in the application process. The affected path is restricted to manipulated action records and does not independently provide database-write access. This issue is fixed in version 2.25.1. | |
| Title | Laravel MagicLink: Insecure Deserialization of MagicLink Actions Leads to Remote Code Execution | |
| Weaknesses | CWE-502 | |
| References |
| |
| Metrics |
cvssV3_1
|