Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-86184 – Authentication Bypass / Account Takeover – Lara Dashboard before 1.3.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86184 is a critical authentication bypass vulnerability in Lara Dashboard, a Laravel-based admin dashboard package, affecting all versions before 1.3.0. The flaw lies in the screenshot-login route, which allows an unauthenticated attacker to authenticate as any registered user simply by knowing their email address, provided the application’s APP_ENV is not set to production. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical) and a CVSS v4.0 score of 9.3 (Critical).

Technical details

  • Root cause: Missing Authentication for Critical Function (CWE-306) in ScreenshotGeneratorLoginController::login(), which logs a user in without verifying a credential or secret.
  • Trigger condition: The endpoint is reachable whenever the application’s APP_ENV is not set to production (e.g., staging, development, or misconfigured environments left internet-facing).
  • Attack vector: A remote, unauthenticated attacker sends a GET /screenshot-login/{email} request using any registered user’s email address to receive a fully authenticated session cookie for that account.
  • Impact: Full account takeover, including administrative accounts. Once authenticated, an attacker can access user administration, application settings, database contents, and achieve arbitrary code execution through the application’s module installer functionality.

Affected software

  • Lara Dashboard (laradashboard/laradashboard) — all versions prior to 1.3.0
  • Fixed in version 1.3.0 and later

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • (CVSS v4.0 also assigned: 9.3, Critical)

Mitigation and recommended actions

  • Immediate: Upgrade Lara Dashboard to version 1.3.0 or later, which removes/secures the screenshot-login authentication bypass.
  • If patching is not immediately possible:
    • Ensure APP_ENV is explicitly set to production on any internet-facing deployment, since the flaw is only exploitable when it is not.
    • Restrict or block external network access to the /screenshot-login/{email} route at the web server, load balancer, or WAF layer.
    • Review authentication logs for unexpected sessions established via the screenshot-login route and rotate credentials/sessions for any accounts that may have been accessed.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Named response header (set-cookie): lara_dashboard_session=
  • Raw response body: /images/logo/lara-dashboard-dark.png

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge