Laravel Debug Page: Cross-Site Scripting When APP_DEBUG Is On

Published as "Laravel: XSS in Debug Page Information"

low Laravel Laravel framework · Last reviewed Nov 1, 2026

CVE: CVE-2026-102279
GHSA: GHSA-jh5r-qr3c-85q8
Packagist: PKSA-d5tc-s1qs-h781
Reported: Sep 29, 2026

Lets an attacker run script in a visitor's browser through the Laravel debug error page, when APP_DEBUG=true and the visitor hovers a tooltip.

Affected and fixed versions

In laravel/framework. Find the row for the version you run, and update to the release next to it.

If you run	Update to	Support
13.0.0 – 13.29.x	13.30.0	Supported
Up to 12.68.x	12.69.0	Supported

Upgrade

Run the line for the branch you are on.

composer require laravel/framework:^13.30.0
composer require laravel/framework:^12.69.0

What this means

When debug mode is on, an attacker can make script run in the browser of someone viewing Laravel's error page. The script runs when that person moves the mouse over a tooltip on the page. This is cross-site scripting (XSS): code from an attacker running as if it came from your site.

Who is affected

Apps on laravel/framework before 12.69.0, or 13.x before 13.30.0, with APP_DEBUG=true. The Laravel advisory says input from the attacker reached a tooltip on the debug page that was allowed to render HTML. Apps running with APP_DEBUG=false don't show that page, so they aren't exposed. The person viewing the page also has to hover over the tooltip.

What to do

Update laravel/framework to 13.30.0 if you're on 13.x, or to 12.69.0 if you're on 12.x. Releases older than 12.x are affected and get no fix. The fix stops the tooltip from rendering that input as HTML.

Reported by Rikuxx0.

Check your app with an agent

Paste this into a coding agent that can read your project, such as Claude Code, Codex or Amp. It checks your composer.lock against the versions above and tells you what to update, without changing anything.

Check whether the PHP project you have access to is affected by this security advisory, and tell me what to update. Do a read-only check: don't edit files, don't run composer update or composer require, and don't try to reproduce the flaw.

Advisory: Laravel Debug Page: Cross-Site Scripting When APP_DEBUG Is On (CVE-2026-102279, GHSA-jh5r-qr3c-85q8)
Details: https://phpnews.net/security/laravel/ghsa-jh5r-qr3c-85q8

Affected versions, as Composer constraints:
- laravel/framework: >=13.0.0,<13.30.0|<12.69.0

Fixed releases on branches that still get security fixes:
- 13.0.0 – 13.29.x: update to 13.30.0
- Up to 12.68.x: update to 12.69.0

1. Find every composer.lock in the project outside vendor/ (a monorepo can have one per app) and read the installed version of each package above. Packages installed as dependencies of other packages count too.
2. Compare each installed version with its constraint: "|" separates alternative ranges, and "," means both bounds apply.
3. For each affected install, read "What this means" at https://phpnews.net/security/laravel/ghsa-jh5r-qr3c-85q8 and check whether the project meets the conditions it describes (a feature in use, a config value, a driver). Say which conditions you could check and which you couldn't.
4. Report a table: lock file | package | installed version | affected (yes, no or unknown) | conditions met (yes, no or unknown) | update to | evidence. For each affected package, give the command that would fix it, without running it: composer update <package> --with-dependencies when it is only installed as a dependency of another package, or composer require with the fixed version when composer.json requires it directly. If the installed version is on a branch with no fixed release listed, say it needs a move to a newer branch.

Sources

← All Laravel advisories