A critical authentication bypass vulnerability in Lara Dashboard before version 1.3.0 allows unauthenticated attackers to gain full administrative access to the application.

The application contains a missing authentication check in the screenshot-login route, specifically within the ScreenshotGeneratorLoginController. An unauthenticated attacker can supply a target email address to the GET /screenshot-login/{email} endpoint to force the application to authenticate them as that user, provided the environment is not set to production.

This vulnerability poses a severe risk to organizational security by enabling complete account takeover. An attacker can gain unauthorized access to user administration, configuration settings, and database contents, and further escalate their impact by installing malicious modules to achieve arbitrary code execution. Given the CVSS score of 9.8, this flaw represents a critical threat to data integrity, confidentiality, and overall system availability.

Immediate Action: Update the Lara Dashboard installation to version 1.3.0 or later immediately to remove the vulnerable controller route.

Proactive Monitoring: Review web server and application access logs for unusual requests to the /screenshot-login/ endpoint, especially those originating from external or unauthorized IP addresses.

Compensating Controls: If an immediate update is not feasible, ensure the application environment is strictly configured to production mode, as the vulnerable code path contains an explicit check that prevents execution in production environments. Additionally, implement WAF rules to block all traffic directed to the /screenshot-login/ URI pattern.

Public Exploit Available: Unknown

This vulnerability is critical and requires immediate attention. Because the flaw allows for complete administrative takeover of the Lara Dashboard application, administrators should prioritize updating to version 1.3.0. Organizations failing to patch should treat the risk as extreme and ensure that the application is running in a production environment to trigger the existing, albeit limited, code-level protection.