Quick answers
- Is CVE-2026-105129 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105129 being exploited in the wild.
- How severe is CVE-2026-105129?
- Medium severity, with a CVSS score of 6.5, published 4 October 2026.
- Which products and versions are affected?
- LaraDashboard before 1.4.8.
- Is there a fix for CVE-2026-105129?
- Yes: fixed in 1.4.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105129 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-105129?
- 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.8
Technical details
The vulnerability is an authorization bypass in the SettingController where the show() method authorizes using the 'view' permission on the Setting model after retrieving it, but this check does not properly enforce permission granularity. An authenticated user with only settings.view permission can query GET /api/settings or /api/settings/{option_name} to retrieve plaintext secrets. The flaw stems from insufficient authorization logic that fails to restrict access based on setting sensitivity or proper role-based permissions.
Affected products
- LaraDashboard LaraDashboard before 1.4.8
Timeline
- 2026-10-04: disclosed