Laravel Pulse authenticated remote code execution through public query method

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2024-55661?

CVE-2024-55661 is a vulnerability classified as Improper Control of Generation of Code, affecting pulse (affected versions: < 1.3.1). This vulnerability is rated High, with a CVSS score of 8.7. Public exploit code or evidence is available for this vulnerability, but that does not confirm exploitation in the wild.

Overview

Original source data

Laravel Pulse is a real-time application performance monitoring tool and dashboard for Laravel applications. A vulnerability has been discovered in Laravel Pulse prior to version 1.3.1 that could allow remote code execution through the public remember() method in the Laravel\Pulse\Livewire\Concerns\RemembersQueries trait. This method is accessible via Livewire components and can be exploited to call arbitrary callables within the application. An authenticated user with access to Laravel Pulse dashboard can execute arbitrary code by calling any function or static method in which the callable is a function or static method and the callable has no parameters or no strict parameter types. The vulnerable to component is remember(callable $query, string $key = '') method in Laravel\Pulse\Livewire\Concerns\RemembersQueries, and the vulnerability affects all Pulse card components that use this trait. Version 1.3.1 contains a patch.

Affected products and scope

  • The Composer package laravel/pulse is affected in all versions < 1.3.1.
  • The vulnerable code is in Laravel\Pulse\Livewire\Concerns\RemembersQueries and affects all Pulse card components that use the trait.
  • Version 1.3.1 is the release identified by the vendor as patched.
  • The record does not provide separate status for parallel branches or deployment defaults, so the actual package version must be checked in each application.

Technical details

Laravel Pulse exposes remember(callable $query, string $key = '') through the Laravel\Pulse\Livewire\Concerns\RemembersQueries trait. Livewire components invoke this method with a callable supplied through component interaction, but the method does not adequately restrict which callable can be executed.

The attacker must have an authenticated account with access to the Laravel Pulse dashboard. A callable that is a function or static method with no parameters, or without strict parameter requirements, can be invoked in the Laravel application context, resulting in arbitrary code execution.

The issue affects all Pulse card components that use the trait. The fixing commit changes remember() from public to protected, preventing it from being called directly through external Livewire component interaction. The record does not fully establish the application's authentication implementation, internal authorization rules, or the complete set of callable targets that may be reachable.

Exploitability

The attack is remotely reachable through Livewire interactions exposed by the Laravel Pulse dashboard. The vendor advisory requires an authenticated user with dashboard access and does not describe a separate action by another victim.

The normalized record characterizes the attack complexity as low. Its scoring entries are not fully consistent about user interaction, so the most reliable operational prerequisite from the advisory is the requirement for an authenticated account with dashboard access.

The record marks public exploit detail as available, and the advisory publishes a representative Livewire interaction showing how a callable can be passed to the vulnerable method. This establishes public technical exploit detail, but the record does not establish exploitation against a specific deployment.

Technical impact

The direct technical outcome is arbitrary code execution in the context of the Laravel application running Pulse. Depending on the application's process privileges and the callable reached, this can cause loss of data confidentiality, unauthorized modification of data or configuration, and reduced application availability.

The privilege condition is an authenticated account with access to the Pulse dashboard, so the advisory does not describe a fully unauthenticated attack path. The record does not establish container escape, host compromise, or impact to adjacent systems, and those outcomes should not be assumed without deployment-specific evidence.

Business impact

An authenticated account with Laravel Pulse dashboard access can bypass the intended query-memory behavior and invoke arbitrary application code. If successfully exploited, the attacker may be able to read or modify data available to the application process, change application state or configuration, or disrupt service.

The practical impact depends on the PHP process privileges, the callable targets present in the application, and the data and services reachable from that application. The record does not report a breach, data loss, or service outage. Operational risk is greater where the Pulse dashboard is exposed to a broad or weakly controlled set of authenticated users.

Remediation

  1. Upgrade laravel/pulse to version 1.3.1, the release identified by the vendor as patched. Confirm that the lockfile, deployment artifact, and running application all use the fixed package.
  2. Review every Pulse card component using Laravel\Pulse\Livewire\Concerns\RemembersQueries and verify that remember() has the protected visibility introduced by the fixing change.
  3. If an immediate upgrade is not possible, temporarily restrict the Laravel Pulse dashboard to trusted administrators and remove access for accounts that do not require it. This reduces exposure temporarily but does not replace the package update.
  4. Review retained Livewire activity and application logs for unusual behavior involving remember. Do not treat the absence of log evidence as proof that exploitation did not occur.

Detection

  1. Check Composer inventory, composer.lock, and deployment pipelines to determine whether the application uses laravel/pulse, then compare the installed package with the affected range.
  2. Identify whether the Laravel Pulse dashboard is enabled or exposed and list the accounts that can access it. Prioritize deployments where dashboard access is available to more than a tightly controlled administrator group.
  3. Inspect source code or deployed artifacts for Laravel\Pulse\Livewire\Concerns\RemembersQueries and Pulse card components that use the trait. After remediation, verify that remember() is no longer public.
  4. If application telemetry records Livewire method names, review unusual interactions involving remember or attempts to invoke functions and static methods from Pulse components. This is a precautionary review, not a vendor-confirmed IOC, and the absence of matching logs does not prove that the system was not exploited.
Sources (14)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.