Quick answers
- Is CVE-2026-120487 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120487 being exploited in the wild.
- How severe is CVE-2026-120487?
- High severity, with a CVSS score of 7.2, published 2 November 2026.
- Which products and versions are affected?
- LaraDashboard before 1.4.5.
- Is there a fix for CVE-2026-120487?
- Yes: fixed in 1.4.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120487 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-120487?
- Check whether you run LaraDashboard at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.4.5
Technical details
The SettingPolicy::manageCoreUpgrades() method checks only for the 'settings.edit' permission instead of requiring Superadmin role, allowing any administrator with that permission to call /admin/settings/core-upgrades operations. This affects backup, download, restore, and upgrade actions, exposing sensitive database information and allowing unauthorized system modifications. The fix restricts these operations to the intended roles via authorization checks in the CoreUpgradeController.
Affected products
- LaraDashboard LaraDashboard before 1.4.5
Timeline
- 2026-11-02: disclosed