Description
LaraDashboard versions 0.9.2 through 1.2.2 contain a path traversal vulnerability in the core-upgrade backup handling. CoreUpgradeController and BackupService (e.g. BackupService::deleteBackup()) concatenate the user-supplied backup_file/filename value directly onto the backup directory path without normalisation, without applying basename(), and without verifying that the resolved path remains inside storage/app/core-backups; the corresponding form requests only validate the value as a bounded string. An authenticated user holding only the delegated settings.edit permission (not Superadmin) can supply ../ traversal sequences to delete arbitrary files reachable on the host filesystem, including outside the application tree, or to restore a ZIP archive from an arbitrary on-disk location, writing arbitrary files into the application directories and achieving remote code execution. Note: the advisory states the vulnerable concatenation was introduced in the v0.9.7 release line. Fixed in 1.3.0.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| laradashboard | laradashboard | 0.9.2 – < 1.3.0 | 1.3.0 |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
GitHub 1 repository
-
capivara-research/CVE-2026-90932 ★ 1 · Oct 26, 2026
CVE-2026-90932: LaraDashboard path traversal to arbitrary file deletion/write — bilingual analysis and safe PoC
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
References
- GitHub Security Advisory (GHSA-g48h-h5pc-396j) vendor-advisory
- VulnCheck Advisory: LaraDashboard 0.9.2 through 1.2.2 Path Traversal RCE third-party-advisory