/

CVE-2026-86184

Severity:

CRITICAL RISK

(9.8)

Authentication Bypass (CWE-306) in Lara Dashboard App

CVE-2026-86184

Deferred

Vulnerability type

Category:

Authentication Bypass

CWE:

CWE-306

Impact:

Account Takeover and Remote Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Lara Dashboard contains an authentication bypass in its screenshot-login functionality when the application is running outside production mode. An unauthenticated attacker who knows a registered user's email address may obtain a fully authenticated session, potentially reaching administrative functions, database contents, and code execution features.

Affected context

The vulnerability occurs in Lara Dashboard deployments where non-production application settings leave the screenshot-login route available. Risk depends on whether the route is reachable by an untrusted party and whether registered email addresses can be discovered or guessed. A successful authentication bypass may expose user administration, settings, database access, and module installation capabilities.

Exploit preconditions

  • Attack surface: The screenshot-login web route
  • Required access: No prior authentication is required
  • Required information: A registered user's email address may be sufficient
  • Trigger point: Authentication processing for the screenshot-login function
  • Environmental condition: The application must be operating with a non-production

environment configuration that permits the vulnerable behavior

  • Why exploitation is possible: The route can establish an authenticated session

without verifying valid credentials

Why this happens

The underlying flaw is missing authentication enforcement, mapped to CWE-306. A convenience or development-only login mechanism remains accessible under a configuration state that may be reachable in deployed environments. Because the route grants a session based on an email identifier without requiring independent proof of identity, it bypasses the application's normal authentication controls and authorization boundaries.

Potential impact

  • An attacker may take over accounts associated with known email addresses.
  • An attacker could access user administration and application settings.
  • Sensitive database contents may be exposed or modified.
  • Malicious functionality may be installed through the module installer.
  • The application environment could permit arbitrary code execution.
  • Compromised accounts may be used for further lateral movement.

General mitigation guidance

Mitigation generally centers on removing or isolating development-only

authentication paths from reachable deployments.

Common defensive patterns include:

  • Disabling screenshot-login and similar bypass mechanisms by default.
  • Enforcing authentication independently of environment labels or debug modes.
  • Requiring strong, verifiable credentials for every session-establishing route.
  • Applying explicit authorization checks to administrative, database, and

module-management functions.

  • Restricting module installation to trusted administrators and controlled

sources.

  • Separating development configuration from production deployment policies.
  • Running the application with least privilege and limiting database permissions.
  • Treating environment configuration as protected security-sensitive input.

How teams detect issues like this

Organizations can look for:

  • Static analysis rules identifying routes that create sessions without credential

verification.

  • Code review signals such as email-only login logic, debug authentication paths,

and environment checks used as security controls.

  • Integration tests confirming that unauthenticated requests cannot create sessions

under any deployment profile.

  • Runtime monitoring for unexpected requests to screenshot-login or similar routes.
  • Web application firewall or gateway policies blocking development-only endpoints

in controlled environments.

  • Configuration compliance checks that prevent non-production authentication modes

from being enabled on exposed systems.

Automated code-review and security-scanning tools may help identify these patterns,

but should be combined with authorization-focused testing.

Sources

SourceLink
github.comgithub.com/laradashboard/laradashboard
github.comgithub.com/laradashboard/laradashboard/blob/v1.2.2/app/Http/Controllers/Backend/Auth/ScreenshotGeneratorLoginController.php
github.comgithub.com/laradashboard/laradashboard/commit/50986e4ac58c883dd8f064cf32be3e2a87c11b24
github.comgithub.com/laradashboard/laradashboard/releases/tag/v1.3.0
github.comgithub.com/laradashboard/laradashboard/security/advisories/GHSA-wj35-4h53-phfp
vulncheck.comvulncheck.com/advisories/lara-dashboard-before-1.3.0-missing-authentication-in-screenshot-login-route

Frequently asked

questions

It may be remotely exploitable when the screenshot-login route is exposed through

the application and the deployment is using a non-production environment setting.

No prior authenticated session is required.

The attacker generally needs network access to the affected route and a registered

user's email address. They do not need a valid password if the vulnerable login

behavior is active.

Remove or disable the bypass route in deployed environments and require normal,

independently verified authentication for every session-creation path. Administrative

capabilities should also enforce separate authorization checks.

Treat development authentication features as disabled by default, enforce security

controls independently of environment labels, test every deployment profile, and

monitor for exposed debug or convenience-login endpoints.

Find out what's already
exploitable in your codebase.