# CVE-2026-130754: LaraDashboard Account Takeover via Unverified OAuth Email in SocialAuthService


- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-886c-7cx4-2rw7, GHSA-c5x3-wvxj-7cgr

## What is CVE-2026-130754?

CVE-2026-130754 is a critical vulnerability in laradashboard, published on 18 Nov 2026. 

### Official description

All versions of LaraDashboard contain an authentication bypass in SocialAuthService::findOrCreateUser(), which links a social login to an existing account by email without checking that the OAuth provider verified that email. Unauthenticated attackers using an OAuth/OIDC provider that asserts a victim's email can log in as any user, including Superadmin, and keep persistent access through a linked social_accounts entry.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-130754 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130754 is a critical vulnerability in laradashboard, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130754 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-2026-130754/ (Markdown: https://insights.sbomify.com/CVE-2026-130754/index.md)
```

## Sources

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

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