On this page (7 sections)

A critical authentication bypass, tracked as CVE-2026-130754, affects all versions of LaraDashboard. According to the NVD record, the social login code links an incoming social identity to an existing account by email address without checking that the OAuth provider actually verified that email.

If you run LaraDashboard with any social login (OAuth or OIDC) enabled, or you build on its code, treat this as urgent. The research available to us does not list a fixed version, so this article focuses on how the flaw works, how to reduce exposure and how to look for signs of abuse.

What happened

The NVD entry, published on 2026-11-18, describes a flaw in the method SocialAuthService::findOrCreateUser(). When someone signs in through a social provider, this method decides which local account the login belongs to. Instead of relying only on a stable provider identity, it links the login to an existing account by email address. It does not check whether the provider confirmed that the email belongs to the person logging in.

The record states that unauthenticated attackers who use an OAuth/OIDC provider that asserts a victim's email can log in as any user, including Superadmin. They also keep persistent access through a linked social_accounts entry. The NVD record is the only technical text we have; the advisory it references is on GitHub. Only one independent publisher covers this story so far, so details may change as maintainers add information.

Why this weakness is dangerous

Social login rests on one assumption: the identity provider has proven who the user is. An email address in a login response is only a claim. Some providers let people set or change an email without confirming it, and some self-hosted or custom OIDC providers can be configured to assert any address. If an application trusts that claim and uses it to find an existing local account, whoever controls the claim controls the account.

This is a well-known account takeover pattern. Because the target can be the Superadmin account, a successful login gives full administrative control of the application, not just access to one user's data.

The persistence detail matters too. According to the record, the attacker keeps access through a linked social_accounts entry. A password change on the victim account may therefore not be enough on its own; the link itself needs to be reviewed and removed.

Who is realistically exposed

  • Sites running any version of LaraDashboard with at least one social login provider configured.
  • Installations that allow a generic OIDC provider or a provider where emails can be asserted without verification, since the record describes exactly that condition.
  • Instances where an administrator or Superadmin has a known or guessable email address, which is usually the case for company staff.
  • Agencies and hosts that deploy LaraDashboard for clients and may not know social login was switched on.

We cannot tell from the research whether installs with social login fully disabled are reachable. Do not assume they are safe until the maintainers say so; check your configuration and the advisory.

How to check your exposure

Start with facts you can confirm without changing production behavior.

  1. Confirm whether you run LaraDashboard and where (production, staging, client sites). The record says all versions are affected, so the version number alone will not clear you.
  2. Review your login configuration and list every enabled social or OAuth/OIDC provider.
  3. Open the GitHub advisory and check whether a patched release or workaround has been published since this article.
  4. Review recent logins for administrator accounts, looking for sign-ins through a social provider that the account owner does not use.

If you have read access to the application database, this read-only query lists every row in the social_accounts data named in the CVE record, so you can look for linked identities nobody recognizes. Column names are not given in the research, so select all and inspect the result rather than guessing fields. If your installation uses a different table prefix or name, adjust accordingly.

List all linked social logins (read-only, run against the LaraDashboard database)SQL
SELECT * FROM social_accounts;

Look for links attached to Superadmin or other privileged users, creation dates that do not match a login the owner remembers, and provider names your team never enabled.

What to do now

  1. Disable all social login (OAuth/OIDC) providers in LaraDashboard until a fix is confirmed.
  2. Check the maintainers' GitHub advisory for a patched release and apply it as soon as one exists; test on staging first.
  3. Audit the social_accounts entries and remove any link you cannot tie to a real user, starting with Superadmin and other administrators.
  4. Reset passwords for administrator accounts and invalidate active sessions if you find any unexplained link or login.
  5. Turn on multi-factor authentication for local administrator accounts if the application supports it, and restrict the admin area by IP or VPN where practical.
  6. Review administrator activity since social login was enabled: new users, changed settings, installed extensions and exported data.
  7. If you find signs of abuse, follow an incident process: preserve logs, rotate application secrets and API keys, and see our guide on what to do when a website is hacked.
Caution. Disabling a login provider can lock out users who sign in only through social login. Make sure at least one administrator can still sign in with a local password before you change the configuration.
We found no fixed version, vendor workaround or exploitation report in the sources we reviewed. If you maintain your own fork, the general fix pattern is to link accounts only on the provider's stable user ID, and to trust an email only when the provider explicitly marks it as verified.

Detection and monitoring

Authentication bypasses leave few technical traces, because the attacker signs in through a legitimate login flow. Focus on behavior and configuration changes.

  • Alert on sign-ins to administrator accounts from new countries, new devices or unusual hours.
  • Watch for new rows appearing in social_accounts, especially for existing users who never used social login.
  • Log and review OAuth callback requests to your application, and compare them with the logins your staff report.
  • Track changes to admin users, roles and permissions, which an attacker would likely use to persist.

From the outside, you can also confirm that your admin and login pages are not exposed more widely than you intend and that your site's certificate and headers are sound. A read-only scan of a site you have verified, or monitoring for certificate, DNS and header changes, can help with that baseline, though neither can see inside an application's login logic or fix this flaw.

For general hardening of login flows and admin access on small sites, our small business website security guide is a useful companion.

Timeline

Known dates for CVE-2026-130754
DateEvent
2026-11-18CVE record published on NVD with a CVSS score of 9.3 (critical)
2026-11-18Article written; no fixed version, workaround or exploitation reports found in the reviewed sources

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-130754: All versions of LaraDashboard contain an authentication bypass in SocialAuthService::findOrCreateUser(), which links a social login to an existing account by…nvd.nist.gov ·
  • LaraDashboard
  • OAuth
  • Authentication bypass
  • CVE-2026-130754