PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-105129 laradashboard CVE debrief

CVE-2026-105129 is a high-severity vulnerability in LaraDashboard before version 1.4.8. An incorrect authorization issue allows authenticated users with only settings.view permission to read stored secrets via the settings API. This could lead to the exposure of sensitive information such as AI provider API keys, mail credentials, passwords, and tokens.

Vendor
laradashboard
Product
Unknown
CVSS
HIGH 7.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-04
Original CVE updated
2026-10-04
Advisory published
2026-10-04
Advisory updated
2026-10-04

Who should care

Defenders who manage LaraDashboard installations should assess their exposure and prioritize verification of the version in use. This includes reviewing user permissions, access controls, and monitoring for potential unauthorized access to sensitive information. Additionally, security teams should ensure that compensating controls are in place for exposed systems while remediation is scheduled and verified.

Why it matters

CVE-2026-105129 is a high-severity vulnerability in LaraDashboard before version 1.4.8 that allows authenticated users to read stored secrets via the settings API.

  • Verify version of LaraDashboard in use
  • Restrict access to settings API
  • Monitor for unauthorized access

Technical summary

The vulnerability is caused by an incorrect authorization issue in LaraDashboard before version 1.4.8. This allows authenticated users with only settings.view permission to read stored secrets via the settings API, potentially exposing AI provider API keys, mail credentials, passwords, and tokens. The issue arises from inadequate access controls on the settings API, which fails to properly validate user permissions before granting access to sensitive information. To mitigate this vulnerability, it is essential to update LaraDashboard to version 1.4.8 or later and restrict access to the settings API.

Defensive priority

Defenders should prioritize verifying the version of LaraDashboard in use and ensuring that it is updated to 1.4.8 or later. Additionally, defenders should review and restrict access to the settings API to prevent unauthorized access to sensitive information.

Recommended defensive actions

  • Verify the version of LaraDashboard in use and update to 1.4.8 or later
  • Review and restrict access to the settings API
  • Monitor for unauthorized access to sensitive information
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source references indicate that LaraDashboard before version 1.4.8 contains an incorrect authorization vulnerability. The vulnerability allows authenticated users with only settings.view permission to read stored secrets through the settings API. Evidence is limited, so defenders should verify the version in use and review the settings API for potential exposure.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-105129 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-105129

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-105129 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-105129

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.