# GHSA-vr95-p7q6-8m9q: Laravel Cross-site Scripting (XSS) vulnerability in blade templating

> Attackers can inject malicious scripts via Blade component attributes if user input is not sanitized, affecting Laravel 7.x users.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 May 2024

## What is GHSA-vr95-p7q6-8m9q?

GHSA-vr95-p7q6-8m9q is a cross-site scripting vulnerability in laravel/framework, published on 15 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Laravel 7.1.2 addresses a possible XSS related attack vector in the Laravel 7.x Blade Component tag attributes when users are allowed to dictate the value of attributes. All Laravel 7.x users are encouraged to upgrade as soon as possible.

## Which versions are affected by GHSA-vr95-p7q6-8m9q?

2 open source packages ship an affected version, including laravel/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `laravel/framework` | Packagist | From 7.0.0 | 7.1.2 |
| `laravel/framework` | Packagist | From 7.0.0 | 7.1.2 |

## How do I fix GHSA-vr95-p7q6-8m9q?

Upgrade laravel/framework to 7.1.2 or later.

## Is GHSA-vr95-p7q6-8m9q being exploited?

There is no known exploitation of GHSA-vr95-p7q6-8m9q in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-vr95-p7q6-8m9q and fix it if it is affected.

What it is: GHSA-vr95-p7q6-8m9q is a cross-site scripting vulnerability in laravel/framework, published on 15 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-vr95-p7q6-8m9q in the wild and no public exploit code.

Affected packages and fixed versions:
- laravel/framework (Packagist): affected from 7.0.0; fixed in 7.1.2
- laravel/framework (Packagist): affected from 7.0.0; fixed in 7.1.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-vr95-p7q6-8m9q/ (Markdown: https://insights.sbomify.com/GHSA-vr95-p7q6-8m9q/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-vr95-p7q6-8m9q

---
From sbomify Insights: https://insights.sbomify.com/GHSA-vr95-p7q6-8m9q/
Summaries are generated and may contain mistakes; the official description above is the record.