LaraDashboard EUVD-2026-115210

Requires an authenticated LaraDashboard account (versions 1.4.0 up to but not including 1.4.9) holding the read-only email_template.view permission, OR an MCP token that was minted while that permission was held - token abilities are snapshotted at mint time (McpTokenService), so a token can retain mcp:email.send even after permissions change. The MCP interface and its send-email tool must be deployed and network-reachable, since the attacker mints a token and POSTs to /mcp/send-email. The limiting factors are: a valid low-privilege authenticated session or pre-minted token is mandatory (this is NOT remote-unauthenticated), the MCP tooling must be enabled, and only pre-1.4.9 releases are vulnerable; after the fix the tool requires email_template.edit.

The official CVSS 4.0 base is 5.3 (medium): AV:N/AC:L/AT:N means a network-reachable MCP endpoint with low attack complexity and no special attack requirements, but PR:L requires an authenticated low-privilege account (the read-only email_template.view permission) and UI:N means no victim interaction. Impact is confined to integrity of outbound mail (VI:L) with VC:N and VA:N - no data disclosure or service disruption. This is not in CISA KEV, so there is no confirmed active exploitation, and no EPSS probability was supplied, so widespread-exploitation likelihood cannot be quantified from the input. A public PoC reference (a bash relay script) is embedded in the GHSA advisory, but it is not verified as working exploit code. The vuln.today decision label is this_month, consistent with a patch-on-normal-cycle priority rather than an emergency. Signal conflict worth noting: the GHSA advisory proposes a markedly higher vector (S:C/C:N/I:H/A:L) than the assigned CVSS 4.0 (VI:L/SC:N), reflecting a dispute over whether impersonated outbound email constitutes a scope change and high integrity impact - verify severity expectations against the vendor advisory. Overall this is a genuine authorization flaw but a moderate one: the authenticated-account prerequisite and integrity-only impact make it a real priority to patch, not a drop-everything emergency.

A low-privileged or compromised LaraDashboard account holding only the read-only email_template.view permission mints an MCP token with the mcp:email.send ability and POSTs to /mcp/send-email with an attacker-chosen recipient, subject, and raw HTML body, delivering credential-phishing or spam from the organization's own mailer and abusing its domain reputation. Because the body is rendered raw (unsanitized HTML) in the recipient's mail client, phishing payloads display as intended. A public PoC bash script is published in the GHSA advisory, though it is not verified as working exploit code; the attack is network-borne with low complexity but requires an authenticated session/token.