DOM-based XSS in Laravel framework exception debug tooltips

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-2026-102279?

CVE-2026-102279 is a vulnerability classified as Improper Neutralization of Script-Related HTML Tags in a Web Page, affecting framework (affected versions: < 12.69.0 and >= 13.0.0, < 13.30.0). This vulnerability is rated Low, with a CVSS score of 3.1. Current sources do not report this vulnerability as exploited.

Overview

Original source data

Laravel is a web application framework. Prior to 12.69.0 and 13.30.0, Laravel exception debug pages with APP_DEBUG=true pass attacker-controlled input to a Tippy.js tooltip configured with allowHTML true, enabling DOM-based cross-site scripting when a user hovers over the tooltip. This issue is fixed in versions 12.69.0 and 13.30.0.

Affected products and scope

  • laravel/framework versions < 12.69.0 are recorded as affected.
  • laravel/framework versions >= 13.0.0, < 13.30.0 are recorded as affected.
  • The 12.x branch is fixed in 12.69.0.
  • The 13.x branch is fixed in 13.30.0.
  • The supplied affected data does not enumerate additional parallel branches.

Technical details

This is a CWE-80 flaw in Laravel's exception debug page rendering. When APP_DEBUG=true, attacker-controlled data is passed to a Tippy.js tooltip configured with allowHTML=true, causing the browser to interpret the content as HTML. When a user hovers over the tooltip, malicious content can execute as DOM-based XSS. The conditions include a network request that produces an exception debug page, attacker-controlled input reaching that page, and user interaction with the tooltip. The record characterizes the attack as unauthenticated, high complexity, and requiring user interaction. The patch changes the exception renderer so ordinary tooltips disable HTML processing while explicitly designated HTML content is handled separately. The record does not identify the precise input source or payload format.

Exploitability

  • The issue is reachable over the network, and the record does not require attacker authentication.
  • The affected condition is APP_DEBUG=true together with a request that produces a Laravel exception debug page.
  • The recorded attack complexity is high because attacker-controlled input must reach the relevant tooltip.
  • User interaction is required: the user must hover over the tooltip before the DOM-based XSS is triggered.
  • The record marks public_exploit as false and does not confirm active exploitation. This does not prove that exploitation is impossible or has never occurred.

Technical impact

This is a DOM-based XSS issue with unchanged scope and a recorded client-side integrity consequence, not a flaw described as causing confidentiality or availability loss. If successfully exploited, the attacker may affect page content or behavior within the browser context of the user who interacts with the tooltip. The record provides no evidence of server-side code execution, Laravel privilege escalation, or direct impact on server processes. Practical risk depends on whether the debug page is network-reachable and whether a user views and hovers over the tooltip.

Business impact

The flaw can allow an attacker to alter rendered content or trigger actions in the browser context of a user viewing an affected exception debug page. The primary consequence is client-side integrity impact and depends on the user opening the page and interacting with the tooltip. Successful exploitation does not by itself establish server-side code execution or server compromise. The record does not establish data loss, service interruption, or a specific breach scenario.

Remediation

  1. Update laravel/framework to 12.69.0 when the application uses the 12.x branch, or to 13.30.0 when it uses the 13.x branch.
  2. Until the update is applied, set APP_DEBUG=false in reachable environments that do not require debug pages. This mitigation follows from the stated prerequisite and does not replace the framework update.
  3. Verify the version actually present in the deployment artifact, Composer metadata, or lockfile after updating rather than checking only the source project's constraint.
  4. Retest the exception renderer and tooltip behavior after updating, especially if the project customizes exception-page assets or rendering.

Detection

  1. Inventory applications using the Composer package laravel/framework, including the version present in deployment metadata or the lockfile.
  2. Check the effective APP_DEBUG value in every network-reachable environment, especially environments that can display exception debug pages.
  3. Identify request paths that can cause the application to render an exception debug page from untrusted input.
  4. In a controlled test environment, inspect the exception renderer and tooltip behavior to determine whether untrusted content is still processed as HTML.
  5. Review application and reverse-proxy logs for requests that generate debug pages as a precaution. This is not a confirmed indicator, and the absence of matching log entries does not prove that a system is safe.
Sources (21)
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.