phenixdigital phoenix_storybook up to 1.0.x Control Message component_iframe_live.ex Query authorization

Summaryinfo

A vulnerability was found in phenixdigital phoenix_storybook up to 1.0.x. It has been classified as critical. The affected element is an unknown function in the library lib/phoenix_storybook/live/story/component_iframe_live.ex of the component Control Message Handler. Performing a manipulation of the argument Query results in authorization. This vulnerability is reported as CVE-2026-47068. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical has been found in phenixdigital phoenix_storybook up to 1.0.x. This affects an unknown code block in the library lib/phoenix_storybook/live/story/component_iframe_live.ex of the component Control Message Handler. The manipulation of the argument query with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Authorization Bypass Through User-Controlled Key vulnerability in phenixdigital phoenix_storybook allows cross-session PubSub topic injection via a URL query parameter. 'Elixir.PhoenixStorybook.Story.ComponentIframeLive':handle_params/3 in lib/phoenix_storybook/live/story/component_iframe_live.ex reads a PubSub topic directly from params["topic"] and broadcasts {:component_iframe_pid, self()} on it with no check that the topic belongs to the requesting session. The shared PhoenixStorybook.PubSub is used to coordinate playground LiveViews with their iframes: a playground subscribes to a session-specific topic and uses the received iframe pid to direct subsequent control messages (variation state, theme switches, extra-assign payloads) via send/2. Because the iframe trusts the query parameter, an attacker who loads /storybook/iframe/<story>?topic=<victim_topic> causes their iframe process pid to be announced on the victim's topic. The victim's playground then addresses its private messages to the attacker's iframe process. This issue affects phoenix_storybook from 0.4.0 before 1.1.0.

The weakness was disclosed by Peter Ullrich and Jonatan Männchen. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-47068 since 05/18/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 1.1.0 eliminates this vulnerability. Applying the patch 6ee03f1c738d4436dde1b066cf65c80663d489f5 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-31111). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• phenixdigital

Name

• phoenix_storybook

Version

• 1.0

Website

• Product: https://github.com/phenixdigital/phoenix_storybook/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion