CVE-2026-130754 is a critical authentication bypass in LaraDashboard's social login flow. An unauthenticated attacker can sign in as any user, including Superadmin, by using an OAuth/OIDC provider that asserts the victim's email address.
What Is It
The flaw is in SocialAuthService::findOrCreateUser(). When a user signs in through a social login, LaraDashboard finds an existing account with the same email address and links the login to it. It does not check whether the OAuth provider actually verified that email.
An attacker who controls, or can use, an OAuth/OIDC provider that claims a victim's email can therefore log in as that victim. The successful login also creates a linked social_accounts entry, so the attacker keeps persistent access to the account.
The weakness is classified as CWE-287 (Improper Authentication). VulnCheck disclosed it, and the record was published on November 18, 2026. NVD lists its status as "Deferred."
Why It Matters
Both scoring sources rate the issue critical:
- CVSS 3.1: 9.8 CRITICAL (
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) - CVSS 4.0: 9.3 CRITICAL (VulnCheck, secondary)
The vectors describe a network-reachable, low-complexity attack that needs no privileges and no user interaction. Confidentiality, integrity and availability impacts are all high. Superadmin accounts are explicitly in reach, so a successful attack can mean full administrative control of the application. Because the attacker's social login stays linked, resetting the password may not remove their access.
The supplied CISA KEV data contains no entry for this CVE, so KEV does not confirm active exploitation. The CVSS 4.0 exploit maturity field is also "Not Defined."
What's Vulnerable
- Vendor/Product: laradashboard / LaraDashboard
- Package:
pkg:githubactions/laradashboard/laradashboard - Affected versions: from 0 up to and including 1.5.4 (semver)
The NVD description states that "all versions" of LaraDashboard are affected. The record lists no affected CPEs.
Patch Status
The supplied data does not name a fixed version. The affected range runs through 1.5.4, and the description covers all versions. No KEV required action or remediation due date applies, because there is no KEV entry.
Administrators should check the GitHub security advisory below for current fix guidance. They should also review existing social_accounts links on privileged accounts, especially Superadmin, for entries they don't recognize.