# CVE-2026-105128: LaraDashboard before 1.4.8 Open Redirect via Email Template Builder redirect_url

> Attackers can redirect logged-in users to malicious sites via unvalidated redirect parameters in the email template builder.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-4h8m-c92p-4pmv, GHSA-j2vp-w788-8fcf

## What is CVE-2026-105128?

CVE-2026-105128 is a medium-severity vulnerability in laradashboard, published on 3 Oct 2026. 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

LaraDashboard before 1.4.8 contains an open redirect vulnerability that allows remote attackers to redirect users by supplying an unvalidated redirect_url parameter to EmailTemplateController builder and builderEdit. Attackers can send crafted builder links to logged-in users with email template permissions so saving a template navigates them to attacker-controlled phishing sites.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-105128?


## How do I fix CVE-2026-105128?

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

## Is CVE-2026-105128 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105128 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105128 and fix it if it is affected.

What it is: CVE-2026-105128 is a medium-severity vulnerability in laradashboard, published on 3 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105128 exists.

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

## Sources

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

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