CVE-2026-120450

LaraDashboard MCP email tool grants sending to template readers

LaraDashboard · MCP send-email tool

First documented disclosure · Review checkpoint

Summary

A read-only template permission can authorize arbitrary outbound email.

Severity and exploitation evidence

Medium · 5.3/10 · CVSS 4.0. Severity source.

Exploitation not established: Published researcher reproduction; malicious exploitation and victim counts are not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The MCP sending tool checks email_template.view instead of a write-capable permission.

Conditions required

An authenticated user permitted to obtain/use an MCP token, with email_template.view and a configured site mailer.

Potential impact

Attacker-chosen recipients, subjects and HTML can use the application’s mail identity for phishing or spam.

Affected versions and configurations

CNA: >=1.4.0 and <1.4.9; original advisory tested 1.4.2.

Fix and mitigation status

1.4.9 for this authorization flaw.

Practical next steps

Upgrade; the fix requires email_template.edit. Reassess MCP token permissions and audit unexpected sending.

Operating lesson

Read access to templates must not imply authority to send messages.

Evidence and limits

November 1 public fix/advisory precedes November 2 CVE. VulnCheck scores Medium 5.3 CVSS 4.0; GHSA labels the broader report High and retains a stale no-fix table. This CVE covers sending authorization, not every token-lifecycle claim in that report.

Sources