LaraDashboard before 1.4.5 Incorrect Authorization via SettingPolicy Core Upgrades
LaraDashboard 1.4.2 and earlier lets users with the settings.edit permission, which the Admin role holds by default, create and download full backups. CVSS rates it High (8.6). Fixed in 1.4.5.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.4.5
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. LaraDashboard version 1.4.2 or earlier is affected Attacker holds the ordinary settings.edit permission, which the Admin role has by default
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.4.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
LaraDashboard before 1.4.5 contains an incorrect authorization vulnerability in SettingPolicy::manageCoreUpgrades() that allows non-Superadmin administrators with settings.edit to access Superadmin-only core-upgrade operations. Attackers can use the /admin/settings/core-upgrades backup, download, restore and upgrade actions to obtain database dumps containing password hashes and restore or upgrade the site.
What to do
Check whether your setup matches what the bug needs.
LaraDashboard version 1.4.2 or earlier is affected Attacker holds the ordinary settings.edit permission, which the Admin role has by defaultUpgrade to a fixed version: 1.4.5.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- LaraDashboard LaraDashboard
fixed in 1.4.5
Evidence 5
- Advisory
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120487
What does this mean?
The settings.edit permission grants access to backup functions it should not. Holders can create and download full backups, which include application source, database dumps with user password hashes, and settings, and can also restore, upgrade, or delete backups.Source: github.com
Am I affected, and how do I check?
Versions 1.4.2 and earlier are listed as affected, and the advisory says the flaw has been present since v1.0.x. To check an installation, look at the installed LaraDashboard version and at which roles or users hold the settings.edit permission.Source: github.com
What should I do about it?
Upgrade to LaraDashboard 1.4.5, the first fixed version.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data