CVE-2026-61701: CWE-502: Deserialization of Untrusted Data in cesargb laravel-magiclink
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.
AI Analysis
Technical Summary
CVE-2026-61701 is a deserialization of untrusted data vulnerability (CWE-502) in the cesargb laravel-magiclink package. Versions >=2.0.0 and <2.25.1 store serialized action objects in the magic_links.action database column and deserialize them through src/MagicLink.php and src/Actions/ResponseAction.php without sufficient integrity checks. An unsafe legacy unserialize() fallback remains reachable, enabling an attacker who can manipulate database records to insert malicious serialized objects containing executable closures. When a user visits the crafted magic link, the application deserializes the malicious object, potentially executing arbitrary code within the application process. The vulnerability requires the attacker to have database write capabilities through other means and does not independently grant such access. The vulnerability is resolved in version 2.25.1.
Potential Impact
Successful exploitation allows an attacker with database write access to execute arbitrary code within the application process by injecting malicious serialized objects. This can lead to full compromise of the application, including confidentiality, integrity, and availability impacts. However, the vulnerability does not provide direct database write access and requires a separate vector to manipulate database records.
Mitigation Recommendations
Upgrade laravel-magiclink to version 2.25.1 or later, where this vulnerability is fixed. Until then, ensure that database write access is tightly controlled and monitor for any unauthorized modifications to the magic_links.action column. Patch status is confirmed fixed in 2.25.1.
CVE-2026-61701: CWE-502: Deserialization of Untrusted Data in cesargb laravel-magiclink
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.
CVSS v3.1
Score 8.8high
Affected software
cesargb
laravel-magiclink
pkg:github/cesargb/laravel-magiclinkRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-61701 is a deserialization of untrusted data vulnerability (CWE-502) in the cesargb laravel-magiclink package. Versions >=2.0.0 and <2.25.1 store serialized action objects in the magic_links.action database column and deserialize them through src/MagicLink.php and src/Actions/ResponseAction.php without sufficient integrity checks. An unsafe legacy unserialize() fallback remains reachable, enabling an attacker who can manipulate database records to insert malicious serialized objects containing executable closures. When a user visits the crafted magic link, the application deserializes the malicious object, potentially executing arbitrary code within the application process. The vulnerability requires the attacker to have database write capabilities through other means and does not independently grant such access. The vulnerability is resolved in version 2.25.1.
Potential Impact
Successful exploitation allows an attacker with database write access to execute arbitrary code within the application process by injecting malicious serialized objects. This can lead to full compromise of the application, including confidentiality, integrity, and availability impacts. However, the vulnerability does not provide direct database write access and requires a separate vector to manipulate database records.
Mitigation Recommendations
Upgrade laravel-magiclink to version 2.25.1 or later, where this vulnerability is fixed. Until then, ensure that database write access is tightly controlled and monitor for any unauthorized modifications to the magic_links.action column. Patch status is confirmed fixed in 2.25.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-10T18:51:13.919Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa81e7d55bf5e2cf54cc38c
Added to database: 09/14/2026, 16:19:09 UTC
Last enriched: 09/14/2026, 16:32:12 UTC
Last updated: 09/15/2026, 03:17:49 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.