CVE-2026-61701

8.8

cesargb · laravel-magiclink

Laravel MagicLink is vulnerable to insecure deserialization of untrusted data in versions 2.0.0 through 2.25.0, allowing attackers with database access to execute arbitrary code.

Executive summary

A critical deserialization vulnerability in the cesargb laravel-magiclink package permits remote code execution for attackers who can influence database contents.

Vulnerability

This flaw involves the deserialization of untrusted data (CWE-502) within the magic_links.action database column. An authenticated attacker capable of modifying database records can inject a malicious serialized object, which is then executed by the application during the link validation process.

Business impact

The ability to execute arbitrary code on the application server represents a critical risk to business operations and data integrity. A successful exploit could lead to full system compromise, unauthorized access to sensitive user data, and potential lateral movement within the network. With a CVSS score of 8.8, this vulnerability is classified as High severity and demands immediate attention to prevent total loss of service or data exfiltration.

Remediation

Immediate Action: Update the laravel-magiclink package to version 2.25.1 or later immediately to remove the unsafe deserialization path.

Proactive Monitoring: Review database logs for unauthorized or unexpected modifications to the magic_links table, specifically looking for serialized data patterns.

Compensating Controls: Ensure that database access is strictly audited and limited to authorized services, and employ application-level input validation to prevent SQL injection, which is a prerequisite for this exploit.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the potential for arbitrary code execution, this vulnerability poses a significant risk to any environment utilizing the affected package. Administrators should prioritize the update to version 2.25.1 as part of their next maintenance cycle or sooner if the application is exposed to high-risk threats. Verifying the integrity of database records is also recommended to ensure no malicious payloads have already been introduced.

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources