Skip to main content
VulnerabilityPublished Updated

CVE-2026-47068: phenixdigital phoenix_storybook · Insecure Direct Object Reference

Affects phenixdigital phoenix_storybookSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low : upgrade to 1.1.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.1.0, 6ee03f1c738d4436dde1b066cf65c80663d489f5
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade phoenix_storybook to 1.1.0; phoenix_storybook to 6ee03f1c738d4436dde1b066cf65c80663d489f5.

Affected software

ProductAffectedFixed in
phenixdigitalphoenix_storybookAffected
  • >=0.4.0 <1.1.0
Fixed in
  • 1.1.0
phenixdigitalphoenix_storybookAffected
  • ≥ 8c2c97b0f505780fee4069988bf86736f51d35d7, < 6ee03f1c738d4436dde1b066cf65c80663d489f5
Fixed in
  • 6ee03f1c738d4436dde1b066cf65c80663d489f5
Hexphoenix_storybookpkg:hex/phoenix_storybookOther threatsAffected
  • >=0.4.0 <1.1.0
Fixed in
  • 1.1.0

CPE configurations (1)

  • cpe:2.3:a:phenixdigital:phoenix_storybook:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, avoid exposing phoenix_storybook instances to untrusted users or networks. Review and restrict access to the affected versions (0.4.0 before 1.1.0). Consider implementing additional validation on PubSub topic parameters to ensure they belong to the requesting session if modifying the source code is feasible.

Description

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.

References

Community reviews

Loading reviews…