CVE 9.5 CRITICAL

Unauthenticated remote code execution via HEEx template injection in phoenix_storybook playground_CVE-2026-8467

9.5 / 10
CRITICAL
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Description

Code Injection vulnerability in phenixdigital phoenix_storybook allows unauthenticated remote code execution via unsanitized attribute value interpolation in HEEx template generation.

The psb-assign WebSocket event handler in 'Elixir.PhoenixStorybook.Story.PlaygroundPreviewLive':handle_event/3 accepts arbitrary attribute names and values from unauthenticated clients. These values are passed to 'Elixir.PhoenixStorybook.Helpers.ExtraAssignsHelpers':handle_set_variation_assign/3, which stores them verbatim. When rendering, 'Elixir.PhoenixStorybook.Rendering.ComponentRenderer':attributes_markup/1 interpolates binary attribute values directly into a HEEx template string as name="<val>" without escaping double quotes or HEEx expression delimiters. An attacker can supply a value containing a closing quote followed by a HEEx expression block (e.g. foo" injected={EXPR} bar="), which causes EXPR to be treated as an inline Elixir expression. The resulting template is compiled via EEx.compile_string/2 and executed via Code.eval_quoted_with_env/3 with full Kernel imports and no sandbox, giving the attacker arbitrary code execution on the server.

This issue affects phoenix_storybook from 0.5.0 before 1.1.0.

AI Analysis

Unauthenticated remote code execution via HEEx template injection in phoenix_storybook playground

Basic Information

ID CVE-2026-8467
Source EEF
Published May 20, 2026 at 13:35

Affected Product

Vendor phenixdigital
Product phoenix_storybook
Version 0.5.0
Affected Versions phenixdigital phoenix_storybook 0.5.0
phenixdigital phoenix_storybook e35379dfe2ef1a71b141899e36f431017c55265d

CWE Classification

AI Assessment

AI Score 9.5 / 10
AI Severity Critical
Vendor Phenixdigital
Product phoenix_storybook
Version 0.5.0

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.