# CVE-2025-66509: LaraDashboard: 1-Click Pre-Auth RCE via Host Header + Module Installation Chain

> Attackers can achieve remote code execution by exploiting Host header trust in password resets to hijack admin tokens and trigger module installation.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-j9mm-c9cj-pc82

## What is CVE-2025-66509?

CVE-2025-66509 is a high-severity authentication bypass vulnerability in laradashboard, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LaraDashboard is an all-In-one solution to start a Laravel Application. In 2.3.0 and earlier, the password reset flow trusts the Host header, allowing attackers to redirect the administrator’s reset token to an attacker-controlled server. This can be combined with the module installation process to automatically execute the ServiceProvider::boot() method, enabling arbitrary PHP code execution.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Laradashboard Lara Dashboard.

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

No fix has been published for CVE-2025-66509 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-66509 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66509 is a high-severity authentication bypass vulnerability in laradashboard, published on 4 Dec 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-66509 in the wild and no public exploit code.

Affected product: laradashboard. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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