Skip to main content
Menu
CVEs

CVE

LaraDashboard authentication bypass in SocialAuthService

Affects LaraDashboard 1.5.4 and earlier when an OAuth or OIDC provider can assert an email that matches an existing local account. CVSS rates it critical at 9.3, and no vendor rating is given.

CVE-2026-130754Published Updated Summary written by a model

9.3CriticalCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Do first: Workaround: The checked facts do not name a workaround. Limiting or disabling social login, or reviewing which providers and custom AUTH_SOCIAL_LOGIN_PROVIDERS entries are configured, are the only steps the facts suggest, and they are not confirmed as fixes.

Summary

LaraDashboard, in all versions, has an authentication bypass in its social login code that links a social sign-in to an existing account based only on email, without confirming the provider verified that email. A remote attacker who has no login can use a provider that asserts a victim's email to sign in as that user, including a Superadmin, and keep access through a linked social account.

Original 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.

cve.now Index

31Pcve.now Index 31 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.3/10CVSS 9.3
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 36 if advisories confirm default setups are exposed

What to do

  • Workaround: The checked facts do not name a workaround. Limiting or disabling social login, or reviewing which providers and custom AUTH_SOCIAL_LOGIN_PROVIDERS entries are configured, are the only steps the facts suggest, and they are not confirmed as fixes.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130754 (LaraDashboard Account Takeover via Unverified OAuth Email in SocialAuthService), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130754 (entry last updated 2026-11-18):
Affected:
- laradashboard laradashboard: through 1.5.4
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Attacker can get an OAuth/OIDC provider to assert an arbitrary email address (certain providers, misconfigured providers, or a custom provider added via AUTH_SOCIAL_LOGIN_PROVIDERS). (source: https://github.com/laradashboard/laradashboard/security/advisories/GHSA-c5x3-wvxj-7cgr)
- A local user account already exists with the same email address as the one the provider returns. (source: https://github.com/laradashboard/laradashboard/security/advisories/GHSA-c5x3-wvxj-7cgr)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130754 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130754 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/laradashboard/laradashboard/security/advisories/GHSA-c5x3-wvxj-7cgr
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130754
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130754"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

  • laradashboard laradashboard

    through 1.5.4

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · laradashboard/laradashboard · Advisory GHSA-c5x3-wvxj-7cgr
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130754
RecordNVD · CVE-2026-130754

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130754

Is CVE-2026-130754 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The SocialAuthService links a social login to an existing local account by matching the email address the OAuth provider returns. If a provider asserts an arbitrary email, a user can be logged in as that account with no password, including a Superadmin, and can keep re-entry through a linked social_accounts entry.Source: github.com

Which versions are affected by CVE-2026-130754?

laradashboard: through 1.5.4.Source: cve.now feed data

Am I affected, and how do I check?

Versions 1.5.4 and earlier are listed as affected. The exposure needs a provider that can assert an arbitrary email, such as certain providers, misconfigured providers, or a custom provider added through AUTH_SOCIAL_LOGIN_PROVIDERS, plus a local account with the same email. To check, look at the installed LaraDashboard version and whether AUTH_SOCIAL_LOGIN_PROVIDERS adds custom social login providers.Source: github.com

How do I fix CVE-2026-130754?

The checked facts name no fixed version or vendor patch identifiers for this vulnerability. Check the vendor's advisory for a fix before relying on any upgrade.Source: github.com

What if there's no patch?

The checked facts do not name a workaround. Limiting or disabling social login, or reviewing which providers and custom AUTH_SOCIAL_LOGIN_PROVIDERS entries are configured, are the only steps the facts suggest, and they are not confirmed as fixes.Source: github.com

More CVEs