# CVE-2025-27515: Laravel has a File Validation Bypass

> Attackers can bypass file validation rules in Laravel applications using wildcard validation, potentially uploading malicious files.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Mar 2025
- **Updated:** 5 Mar 2025
- **Also known as:** BIT-laravel-2025-27515, CLSA-2025-1761785337, CLSA-2025-1761785347, CLSA-2026-1779842936, CLSA-2026-1783558967, CLSA-2026-1784077493, DEBIAN-CVE-2025-27515, GHSA-78fx-h6xr-vch4, MINI-46wc-6x37-9hcf

## What is CVE-2025-27515?

CVE-2025-27515 is a medium-severity vulnerability in laravel framework, published on 5 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Laravel is a web application framework. When using wildcard validation to validate a given file or image field (`files.*`), a user-crafted malicious request could potentially bypass the validation rules. This vulnerability is fixed in 11.44.1 and 12.1.1.

Weakness: CWE-155 (Improper Neutralization of Wildcards or Matching Symbols)

## Which versions are affected by CVE-2025-27515?

7 open source packages ship an affected version, including laravel/framework and laravel. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `laravel/framework` | Packagist | All versions | 10.48.29 |
| `laravel/framework` | Packagist | All versions | 10.48.29 |
| `laravel/framework` | Packagist | From 11.0.0 | 11.44.1 |
| `laravel/framework` | Packagist | From 11.0.0 | 11.44.1 |
| `laravel/framework` | Packagist | From 12.0.0 | 12.1.1 |
| `laravel/framework` | Packagist | From 12.0.0 | 12.1.1 |
| `laravel` | Bitnami | All versions | 12.2.0 |

Products: Laravel Framework.

## How do I fix CVE-2025-27515?

Upgrade laravel/framework to a fixed version for your release line: 10.48.29, 11.44.1 or 12.1.1.

## Is CVE-2025-27515 being exploited?

There is no known exploitation of CVE-2025-27515 in the wild and no public exploit code.

Public exploit code:

- PoC of CVE-2025-27515 (github_poc): https://github.com/joaovicdev/EXPLOIT-CVE-2025-27515
- Penetration test white-box su un’app Laravel: analisi Cyber Kill Chain, RCE via file upload bypass (CVE-2025-27515), exfiltration e remediation. (github_poc): https://github.com/Shanks2001/Progetto-sicurezza

## Other vulnerabilities in laravel framework

- [CVE-2021-43617](https://insights.sbomify.com/CVE-2021-43617/): File upload in n/a (critical 9.8)
- [CVE-2020-19316](https://insights.sbomify.com/CVE-2020-19316/): OS Command Injection in Laravel Framework (high 8.8)
- [CVE-2018-6330](https://insights.sbomify.com/CVE-2018-6330/): SQL injection in n/a (high 8.8)
- [CVE-2024-13918](https://insights.sbomify.com/CVE-2024-13918/): Laravel Reflected XSS via Request Parameter in Debug-Mode Error Page (high 8.0)
- [CVE-2024-13919](https://insights.sbomify.com/CVE-2024-13919/): Laravel Reflected XSS via Route Parameter in Debug-Mode Error Page (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27515 and fix it if it is affected.

What it is: CVE-2025-27515 is a medium-severity vulnerability in laravel framework, published on 5 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27515 in the wild and no public exploit code.

Affected packages and fixed versions:
- laravel/framework (Packagist): affected all versions; fixed in 10.48.29
- laravel/framework (Packagist): affected all versions; fixed in 10.48.29
- laravel/framework (Packagist): affected from 11.0.0; fixed in 11.44.1
- laravel/framework (Packagist): affected from 11.0.0; fixed in 11.44.1
- laravel/framework (Packagist): affected from 12.0.0; fixed in 12.1.1
- laravel/framework (Packagist): affected from 12.0.0; fixed in 12.1.1
- laravel (Bitnami): affected all versions; fixed in 12.2.0

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/CVE-2025-27515/ (Markdown: https://insights.sbomify.com/CVE-2025-27515/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27515
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27515
- OSV: https://osv.dev/vulnerability/CVE-2025-27515

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27515/
Summaries are generated and may contain mistakes; the official description above is the record.