Account takeover via unauthenticated screenshot login
Published Sep 5, 2026 · Updated Sep 5, 2026
Authentication bypass in LaraDashboard before 1.3.0 allows remote attackers to assume any registered account via the screenshot-login route. ScreenshotGeneratorLoginController::login resolves the attacker-supplied email and calls Auth::login without authentication or signed-token checks. When APP_ENV is not production, a reachable instance grants the selected user's privileges, including Superadmin access and module-based code execution.
Summary
What happened
Authentication bypass in LaraDashboard before 1.3.0 allows remote attackers to assume any registered account via the screenshot-login route. ScreenshotGeneratorLoginController::login resolves the attacker-supplied email and calls Auth::login without authentication or signed-token checks. When APP_ENV is not production, a reachable instance grants the selected user's privileges, including Superadmin access and module-based code execution.
The record
- CVE
- CVE-2026-86184
- Published
- Sep 5, 2026
- Updated
- Sep 5, 2026
- Vendor
- LaraDashboard
- Product
- LaraDashboard
- Classifications
- CWE-306, CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 2026CVE publishedPublication date reported by the CVE source.
- Sep 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub Security Advisory reproduction procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo