
Bilingual analysis and safe lab PoC for CVE-2026-90932, a path traversal in LaraDashboard backup handling enabling arbitrary file deletion and write leading to RCE.
English | Português do Brasil
Public research evidence and safe local-lab reproduction material for a path traversal vulnerability in LaraDashboard's core-upgrade backup handling.
| Field | Value |
|---|---|
| Product | LaraDashboard |
| Official affected range | >= 0.9.2, < 1.3.0 |
| Fixed boundary | 1.3.0 |
| Tested revision | 9dc1335835701651aef3adcb3e885acecb32402c |
| Weakness | CWE-22 |
| Official severity | CVSS 4.0 8.6 / CVSS 3.1 7.2 |
| Required permission | settings.edit (non-Superadmin) |
| Advisory | GHSA-g48h-h5pc-396j |
| CNA / reporter | VulnCheck / capivara-research |
The CVE title retains the originally reported 0.9.2 through 1.2.2 wording.
The canonical record updated on 2026-10-29 expresses the affected range as
>= 0.9.2, < 1.3.0 and marks 1.3.0 unaffected.
CoreUpgradeController and BackupService append the caller-controlled backup_file or filename value directly to the backup directory. They do not normalize the resulting path or verify that it remains inside storage/app/core-backups.
A non-Superadmin user holding the delegatable settings.edit permission can consequently:
../ traversal; androutes, app, config, bootstrap, and vendor.The second vector enables arbitrary file write and can lead to remote code execution.
public function deleteBackup(string $filename): bool
{
$path = $this->backupPath . '/' . $filename;
if (File::exists($path)) {
return File::delete($path);
}
return false;
}
The restore path uses the same pattern:
$backupPath = $this->backupService->getBackupPath() . '/' . $request->validated('backup_file');
Validation only requires a bounded string. Directory components are allowed and no resolved-path containment check is performed.
The original coordinated disclosure reproduced both vectors end to end on a clean local installation with a custom role holding only settings.view and settings.edit.
The poc/ directory contains:
The HTTP PoC refuses non-loopback targets and requires --execute. Create a disposable canary outside the backup directory before using it. Do not target production systems.
For a source-only reproducible check pinned to the audited revision:
docker build -t cve-2026-90932 .
docker run --rm cve-2026-90932
Exit status 1 means vulnerable markers were found; 0 means none were found.
An affected installation permits a delegated settings operator to cross the application's intended permission and filesystem boundaries. Confirmed effects include arbitrary deletion outside the application tree and overwriting application code from an attacker-selected archive.
basename($name) !== $name.realpath().Reported through GitHub Private Vulnerability Reporting and published by the project on 2026-08-30. VulnCheck assigned CVE-2026-90932 on 2026-09-14 and credits capivara-research as reporter.
.
├── README.md / README.pt-BR.md
├── poc/
│ ├── static_verify.py # non-invasive source verifier
│ └── delete_canary.py # explicit, loopback-only canary deletion
├── evidence/official-record-summary.md
├── Dockerfile
├── SECURITY.md
└── LICENSE
Use this material only on systems you own or are explicitly authorized to test. The PoCs are intended for isolated, disposable lab environments.