CVE-2026-105125 laradashboard CVE debrief

Who should care

Defenders responsible for LaraDashboard instances, especially those on Windows hosts, should assess exposure and risk. They should prioritize verifying exposure of LaraDashboard instances, assessing the risk of reading sensitive JSON files, and updating to version 1.4.8 or later if possible. This includes reviewing compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

CVE-2026-105125 is a path traversal vulnerability in LaraDashboard before version 1.4.8 that allows unauthenticated attackers to read JSON files. Defenders should prioritize verifying exposure, assessing risk, and updating to version 1.4.8 or later if possible.

• Verify exposure of LaraDashboard instances to unauthenticated path traversal attacks
• Assess the risk of reading sensitive JSON files
• Prioritize updating to version 1.4.8 or later if possible

Technical summary

The vulnerability allows unauthenticated attackers to read JSON files by manipulating the {lang} route segment. On Windows hosts, attackers can send URL-encoded backslash sequences to escape resources/lang and read composer.json or other application JSON files. This vulnerability has a CVSS score of 6.3 and a severity of MEDIUM. Defenders should prioritize verifying exposure of LaraDashboard instances, especially those on Windows hosts, and assess the risk of reading sensitive JSON files. The CVE record and source references provide information on the vulnerability.

Defensive priority

Defenders should prioritize verifying exposure of LaraDashboard instances, especially those on Windows hosts, and assess the risk of reading sensitive JSON files.

Recommended defensive actions

• Verify exposure of LaraDashboard instances, especially those on Windows hosts
• Assess the risk of reading sensitive JSON files
• Update to version 1.4.8 or later if possible
• 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 provide information on the vulnerability, but details on exploitation, impact, and remediation are limited. Defenders should verify exposure of LaraDashboard instances, especially those on Windows hosts, and assess the risk of reading sensitive JSON files. The CVE record was published on 2026-10-04T00:16:35.990Z and has not been modified since then.

Sources and 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.