Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessForge Host header on reset request
-
DeliveryPoison admin reset email link
-
ExploitCapture admin token via attacker server
-
ExecutionReset password and authenticate as admin
-
PersistUpload malicious module package
-
ImpactExecute arbitrary PHP via ServiceProvider::boot()
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the application's admin password-reset flow to be reachable and for an admin reset to be triggered (attacker-initiated against a known admin email, or awaiting a legitimate one); the attacker supplies a crafted Host header so the generated reset link points to their server. Token capture typically depends on the administrator interacting with the poisoned email link or an email client prefetching it - a real limiting factor the vendor's UI:N rating omits. Achieving RCE additionally requires the module-upload feature to be usable after the resulting admin takeover; in 2.3.0 and earlier uploaded modules could execute immediately, which the patch closes by defaulting new modules to disabled and blocking overwrite of existing module names. |
| Impact | This is a genuinely high-impact chain - Host-header injection in the admin password-reset flow (confirmed by the commit swapping url(route(...)) for config('app.url')) leaks the admin reset token to an attacker-controlled host, and the module-upload feature then auto-executes ServiceProvider::boot() for full PHP RCE (CVSS 4.0 VC:H/VI:H/VA:H). The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N, score 8.9) rates it as remotely exploitable by an unauthenticated attacker with no user interaction, but this conflicts with the mechanics of reset-poisoning: capturing the token realistically depends on an admin-initiated reset and the admin interacting with (or a client prefetching) the poisoned link, so AC:L/UI:N likely understates attack complexity and interaction requirements. Countervailing signals lower real-world urgency: EPSS is only 0.11% (29th percentile), the CVE is NOT in CISA KEV, and the affected product is a niche open-source Laravel starter kit with a small deployment footprint. The CVSS 4.0 threat metric E:P indicates proof-of-concept exploit maturity, but no public exploit URL is present in the references. Net: a serious, patch-worthy flaw for anyone actually running LaraDashboard ≤2.3.0, but low predicted mass exploitation - treat as high priority for affected operators, not an emergency fleet-wide fire drill. |
| Exploit ScenarioDerived | An attacker submits a password-reset request for the administrator account while injecting a forged Host header, causing the reset email to contain a link pointing to an attacker-controlled server. When the admin interacts with the poisoned link (or a mail client prefetches it), the reset token is captured by the attacker, who resets the admin password, logs in, and uploads a malicious module whose ServiceProvider::boot() method executes arbitrary PHP. No public exploit URL is referenced, though the CVSS 4.0 threat metric E:P indicates proof-of-concept maturity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 18, 2026
Host-header injection in LaraDashboard 2.3.0 and earlier allows remote attackers to poison the administrator password-reset link and redirect the reset token to an attacker-controlled host, enabling admin account takeover and, via the module installer, arbitrary PHP code execution. The reset URL is built with url(route(...)) rather than config('app.url'), so a crafted Host header controls the link; token capture still depends on administrator interaction or mail prefetching, and RCE requires module upload after takeover. No public exploit identified at time of analysis; vendor patch commit/advisory exist, and EPSS is 0.11% (29th percentile).
Earlier versions of this analysis (1)
RemediationAI
Apply the vendor fix by upgrading to a LaraDashboard release containing commit cc42f9cdf8e59bce794ee2d812a9709b1e6efa87 and review advisory https://github.com/laradashboard/laradashboard/security/advisories/GHSA-j9mm-c9cj-pc82; patch status is 'Upstream fix available (PR/commit); released patched version not independently confirmed,' so confirm the target release includes the commit. If immediate upgrade is not possible, enforce a strict Host-header allowlist at the reverse proxy and Laravel trusted-host layer so reset emails always use the canonical host (trade-off: misconfigured hosts break legitimate access), and restrict or disable module upload/activation for nonessential users (trade-off: removes self-service module installation). After any suspected reset-token leakage, invalidate outstanding password-reset tokens and active admin sessions and rotate administrator credentials.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
LaraDashboard is a Laravel-based application starter/admin panel. The password-reset notification built the reset URL with Laravel's url(route(..., false)), which derives scheme/host from the incoming request Host header; an attacker who can trigger an admin reset or waits for one can cause the emailed link to point to their server and capture the token. The flaw is mapped to CWE-284 (Improper Access Control), reflecting trust of client-controlled host data in a security-sensitive URL. RCE arises because the module installation path could overwrite or activate modules whose ServiceProvider::boot() runs immediately; the patch uses config('app.url'), blocks overwriting existing modules, reads the actual module name from module.json, and defaults newly uploaded modules to disabled. CPE identifies the Laravel-platform package laradashboard:lara_dashboard through 2.3.0.
Know when Laravel gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
Network-reachable and ultimately unauthenticated (PR:N), but token capture hinges on an admin reset and interaction with the poisoned link, so AC:H and UI:R; full RCE yields C/I/A High.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
5DescriptionCVE.org
LaraDashboard is an all-In-one solution to start a Laravel Application. In 2.3.0 and earlier, the password reset flow trusts the Host header, allowing attackers to redirect the administrator’s reset token to an attacker-controlled server. This can be combined with the module installation process to automatically execute the ServiceProvider::boot() method, enabling arbitrary PHP code execution.
Executive ViewAI
LaraDashboard versions 2.3.0 and earlier contain a critical vulnerability that allows attackers to hijack administrator password reset tokens and execute arbitrary code on affected systems. Organizations using this software face immediate risk of complete system compromise and unauthorized access to sensitive data.
Apply vendor patch. Additionally, implement WAF rules to validate and restrict Host header values to approved domains only, disable the module installation feature if not actively used, and enforce network segmentation to limit lateral movement if compromise occurs.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
In Laravel framework through 5.5.21, remote attackers can obtain sensitive information (such as externally usable passwo
Laravel Livewire v3 through v3.6.3 contains a critical remote code execution vulnerability (CVE-2025-54068, CVSS 9.8) th
LaRecipe versions prior to 2.8.1 contain a Server-Side Template Injection (SSTI) vulnerability that can lead to Remote C
File upload bypass in FreeScout 1.8.206 — patch bypass for CVE-2026-27636. PoC and patch available. CVSS 10.0.
Remote code execution in FreeScout prior to version 1.8.206 allows authenticated users to upload `.htaccess` files that
In Laravel Framework through 5.5.40 and 5.6.x through 5.6.29, remote code execution might occur as a result of an unseri
Dokans SaaS e-commerce platform v3.9.2 has a CVSS 10.0 authentication bypass allowing unauthenticated attackers to obtai
Predictable password reset tokens in FreeScout help desk before 1.8.206. Weak random number generation allows attackers
Bagisto eCommerce platform before 2.3.10 is vulnerable to server-side template injection (SSTI) through customer address
Bagisto eCommerce platform (2.3 branch before 2.3.10) leaves installation API routes active after setup, allowing unauth
A vulnerability was found in laravel 5.1 and classified as problematic. Rated critical severity (CVSS 9.8), this vulnera
Laravel TokenGuard authentication bypass is a genuine high-priority issue, not an inflated CVSS score: unauthenticated a
EUVD-2025-201292
NVD
CVE.org
EPSS
GitHub
Exploit-DB