LaraDashboard 0.9.2 through 1.2.2 Path Traversal RCE
Impact
LaraDashboard versions 0.9.2 through 1.2.2 have a path traversal vulnerability in core-upgrade backup handling, allowing an authenticated user with settings.edit permission to delete or restore arbitrary files. The vulnerability is due to concatenating user-supplied input onto the backup directory path without normalization. This affects versions before 1.3.0.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
laradashboard · VulnCheck
laradashboard
2 ranges
laradashboard · VulnCheck
laradashboard
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0.9.2 → before 1.3.0
semver versions
unaffected
1.3.0
semver versions
Other versions: unaffected
Original source 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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-90932View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Environment requirements
These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.
VulnCheck · platform conditions
Any condition may hold
Vulnerable product
cpe:2.3:a:laradashboard:lara_dashboard:*:*:*:*:*:*:*:*From (inclusive): 0.9.2
Before: 1.3.0
Original applicability statements
[
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:laradashboard:lara_dashboard:*:*:*:*:*:*:*:*",
"versionStartIncluding": "0.9.2",
"versionEndExcluding": "1.3.0"
}
]
}
]
}
]Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.