/

CVE-2026-86437

Severity:

HIGH RISK

(7.2)

Authorization Bypass (CWE-863) in Lara Dashboard Admin

CVE-2026-86437

Deferred

Vulnerability type

Category:

Incorrect Authorization

CWE:

CWE-863

Impact:

Application Code Execution and Sensitive Data Exposure

Severity:

HIGH RISK

(7.2)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Lara Dashboard may allow an administrator with only the settings.edit permission to upload and extract an archive over live application source files. If the archive can alter executable application code, the attacker may achieve command execution as the web server user and access application secrets or database credentials.

Affected context

The issue occurs in Lara Dashboard deployments where the core-upgrade upload endpoint is accessible to non-Superadmin administrators and archive contents are extracted into the live application source tree. Risk increases when authorization checks do not distinguish between routine settings management and operations that can replace executable files.

Exploit preconditions

  • Attack surface: The administrative core-upgrade archive upload endpoint
  • Required access: An authenticated account with the settings.edit permission or equivalent access
  • Trigger point: Upload and extraction of an archive through the upgrade workflow
  • Why exploitation is possible: The endpoint may authorize a lower-privileged administrator and permit archive contents to overwrite executable application files

Why this happens

The underlying defect is an authorization decision that grants a sensitive file-management operation based on a permission intended for ordinary settings changes. This maps to CWE-863: Incorrect Authorization, because the application does not adequately verify whether the requesting administrator has the privilege required to modify executable source code. The risk is compounded when archive extraction lacks strong destination controls, integrity checks, and separation from the live application path.

Potential impact

  • An attacker may execute commands with the privileges of the web server
  • Application secrets and database credentials could be exposed
  • The application could be modified to persist unauthorized access
  • Database records or other application-managed data may be altered
  • The server could be used to access additional internal resources

General mitigation guidance

Mitigation generally focuses on enforcing operation-specific authorization and separating administrative settings functions from code deployment capabilities.

Common defensive patterns include:

  • Require a narrowly scoped, high-privilege role for archive upload and application-code replacement
  • Apply deny-by-default authorization checks at the endpoint and service layers
  • Keep uploaded archives outside the live application source tree until they pass validation and controlled deployment checks
  • Enforce archive path, file-type, size, and destination restrictions
  • Use integrity verification and an explicit deployment process rather than directly extracting untrusted content
  • Run the web application with least privilege and limit access to environment files, credentials, and deployment directories
  • Prefer immutable or read-only application deployments where operationally feasible

How teams detect issues like this

Detection approaches can include:

  • Static analysis and code review rules that compare endpoint sensitivity with required permissions
  • Review of administrative routes that accept archives, filesystem paths, or deployment-related input
  • Testing authorization boundaries with accounts that possess settings permissions but lack deployment privileges
  • Monitoring archive upload, extraction, and application-file modification events
  • Policy enforcement requiring separate approval and audit logging for changes to executable application files
  • Neutral automated security review tools that flag privilege mismatches and unrestricted archive extraction

Sources

SourceLink
github.comgithub.com/laradashboard/laradashboard
github.comgithub.com/laradashboard/laradashboard/blob/v1.3.1/app/Http/Requests/CoreUpgrade/UploadRequest.php#L15-L18
github.comgithub.com/laradashboard/laradashboard/blob/v1.3.1/app/Policies/SettingPolicy.php#L47-L50
github.comgithub.com/laradashboard/laradashboard/blob/v1.3.1/app/Services/CoreUpgradeService.php#L543-L577
github.comgithub.com/laradashboard/laradashboard/commit/738cc1a219ce459323ef1d09c3789075f1b8d2f2
github.comgithub.com/laradashboard/laradashboard/releases/tag/v1.3.2
github.comgithub.com/laradashboard/laradashboard/security/advisories/GHSA-xv98-x5h7-4g7v
vulncheck.comvulncheck.com/advisories/lara-dashboard-before-1.3.2-incorrect-authorization-in-core-upgrade-archive-upload

Frequently asked

questions

An authenticated administrator may be able to exploit it if the account has the lower-level settings permission but is not intended to manage application code or deployments.

It generally requires access to the administrative endpoint, which may be available remotely to authenticated users depending on deployment and network controls.

Enforce a dedicated, high-privilege authorization check for code-affecting upgrade operations and prevent untrusted archives from being extracted directly into the live source tree.

Use operation-specific roles, deny-by-default authorization, isolated deployment workflows, strict archive validation, least-privilege service accounts, and monitoring for executable-file changes.

Find out what's already
exploitable in your codebase.