# GHSA-297g-xg4h-7w4c: Laravel Cross-site Scripting vulnerability in blade templating

> An attacker can inject malicious scripts into Laravel applications via Blade templating, potentially compromising user sessions or data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **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-297g-xg4h-7w4c?

GHSA-297g-xg4h-7w4c is a cross-site scripting vulnerability in illuminate/view, published on 15 May 2024. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

Laravel is prone to a Cross-site Scripting vulnerability in blade templating.

## Which versions are affected by GHSA-297g-xg4h-7w4c?

2 open source packages ship an affected version, including illuminate/view.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `illuminate/view` | Packagist | From 7.0.0 | 7.1.2 |
| `illuminate/view` | Packagist | From 7.0.0 | 7.1.2 |

## How do I fix GHSA-297g-xg4h-7w4c?

Upgrade illuminate/view to 7.1.2 or later.

## Is GHSA-297g-xg4h-7w4c being exploited?

There is no known exploitation of GHSA-297g-xg4h-7w4c in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-297g-xg4h-7w4c and fix it if it is affected.

What it is: GHSA-297g-xg4h-7w4c is a cross-site scripting vulnerability in illuminate/view, published on 15 May 2024. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-297g-xg4h-7w4c in the wild and no public exploit code.

Affected packages and fixed versions:
- illuminate/view (Packagist): affected from 7.0.0; fixed in 7.1.2
- illuminate/view (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-297g-xg4h-7w4c/ (Markdown: https://insights.sbomify.com/GHSA-297g-xg4h-7w4c/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-297g-xg4h-7w4c

---
From sbomify Insights: https://insights.sbomify.com/GHSA-297g-xg4h-7w4c/
Summaries are generated and may contain mistakes; the official description above is the record.