/

CVE-2026-86438

Severity:

HIGH RISK

(7.2)

Missing Authorization (CWE-862) in Lara Dashboard Module

CVE-2026-86438

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Remote Code Execution

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 does not properly authorize the MarketplaceModuleBrowser

installModule Livewire action, allowing administrators without Superadmin

privileges to install marketplace modules. An attacker who can access the

administrative interface may download and automatically activate an

arbitrary PHP module, potentially resulting in remote code execution.

Affected context

The issue occurs in Lara Dashboard deployments before the affected

authorization behavior was corrected, where the MarketplaceModuleBrowser

exposes the installModule Livewire action to administrator roles that are

not Superadmins. Risk is increased when those users can reach the

administrative interface and marketplace traffic is not protected by

authenticated, integrity-preserving transport.

Exploit preconditions

  • Attack surface: The administrative MarketplaceModuleBrowser and its

Livewire installModule action

  • Required access: An authenticated administrator account that lacks

Superadmin privileges

  • Trigger point: A request that causes a marketplace PHP module to be

downloaded and activated

  • Why exploitation is possible: The action does not enforce the

required authorization boundary, and the module installation path can

process attacker-selected PHP code

  • Additional exposure: Unsigned HTTP requests may allow module content

or request data to be altered in transit when transport protections are

insufficient

Why this happens

The underlying bug is a server-side authorization failure. The

installModule action relies on broad administrator access instead of

enforcing a policy that limits module installation to the intended

privileged role, which maps to CWE-862: Missing Authorization. The risk is

compounded when downloaded modules are trusted and activated without strong

provenance, integrity, or transport guarantees.

Potential impact

  • An attacker may execute arbitrary PHP code within the application process.
  • The application and its associated data could be compromised.
  • Attackers could modify application content, settings, or stored data.
  • Credentials and secrets accessible to the application may be exposed.
  • The server could be used for further compromise or lateral movement.

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the server-side

action boundary rather than relying on interface visibility or client-side

controls. Module installation can be restricted by default to a narrowly

defined privileged role, with explicit policy checks performed for every

request. Module sources can be limited to trusted repositories, while

cryptographic signing, authenticated transport, and integrity verification

reduce the risk of tampered content. Environments can also separate module

management from routine administration and run the application with

least-privilege service accounts and filesystem permissions.

How teams detect issues like this

Detection can include static analysis and code review checks for Livewire

actions that perform installation, activation, file writes, or downloads

without an explicit server-side authorization call. Reviewers can examine

whether role checks are enforced consistently on direct requests and not

only in rendered UI controls. Runtime monitoring can alert on module

installation events, unexpected PHP files, unsigned downloads, and

administrative actions performed by non-privileged roles. Policy enforcement

in CI can require authorization tests for every sensitive action, and

automated review tools may help identify missing permission checks.

Sources

SourceLink
github.comgithub.com/laradashboard/laradashboard
github.comgithub.com/laradashboard/laradashboard/blob/v1.3.1/app/Livewire/Marketplace/MarketplaceModuleBrowser.php#L76-L120
github.comgithub.com/laradashboard/laradashboard/blob/v1.3.1/app/Policies/ModulePolicy.php#L32-L38
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-4x9p-vg5m-vr6p
vulncheck.comvulncheck.com/advisories/lara-dashboard-before-1.3.2-missing-authorization-in-marketplace-module-install-action

Frequently asked

questions

An attacker generally needs access to an administrator account that is

permitted to reach the affected marketplace functionality but is not a

Superadmin.

It can be remotely triggered through the application's administrative

interface when that interface is reachable and the attacker has suitable

credentials. The vulnerability is not necessarily exploitable by an

unauthenticated internet user.

Enforce the intended Superadmin authorization check on the server side for

every installModule request, and require trusted, integrity-verified module

sources before activation.

Apply deny-by-default authorization, test direct action requests for each

role, protect administrative transport, and monitor module installation and

activation events.

Find out what's already
exploitable in your codebase.