# Laravel framework susceptible to reflected cross-site scripting

Advisory record · `GHSA-83wp-f5c3-hqqr`

- **Identifiers:** `GHSA-83wp-f5c3-hqqr` · `CVE-2024-13919` · `PKSA-q46n-4fdk-zjr4`
- **State:** Confirmed
- **Severity:** CVSS 8.0 High
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 10 Mar 2025
- **Updated:** 14 Mar 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Mar 2025, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `laravel/framework` (Packagist): affected `>=11.9.0, <11.36.0`; fixed in `11.36.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The laravel/framework package versions 11.9.0 up to 11.35.1 are vulnerable to reflected cross-site scripting, caused by improper encoding of route parameters on the debug-mode error page. The source gives few details on how an attacker delivers the crafted input, but the issue requires the application to be running in debug mode. Upgrade laravel/framework to 11.36.0 or later, and keep debug mode disabled in production.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.0 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N`, from CNA (sba-research)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0053, the 45th percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:27 UTC: First seen by agentprime
- 31 Oct 2026, 14:27 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-83wp-f5c3-hqqr)

## Sources

- [GitHub Advisory Database: GHSA-83wp-f5c3-hqqr](https://github.com/advisories/GHSA-83wp-f5c3-hqqr)
- [OSV: GHSA-83wp-f5c3-hqqr](https://osv.dev/vulnerability/GHSA-83wp-f5c3-hqqr)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-13919>
- <https://github.com/laravel/framework/pull/53869>
- <https://github.com/laravel/framework/commit/45287fb2a91c69bb1c110539b9b7341faf5aee33>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/laravel/framework/CVE-2024-13919.yaml>
- <https://github.com/laravel/framework>
- <https://github.com/laravel/framework/releases/tag/v11.36.0>
- <https://github.com/sbaresearch/advisories/tree/public/2024/SBA-ADV-20241209-02_Laravel_Reflected_XSS_via_Route_Parameter_in_Debug-Mode_Error_Page>
- <http://www.openwall.com/lists/oss-security/2025/03/10/4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-83wp-f5c3-hqqr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-83wp-f5c3-hqqr/>. Everything for agents: <https://agentprime.io/llms.txt>.
