CVE-2026-15098 Cross-site scripting in Real3D Flipbook – 3D FlipBook, PDF FlipBook, PDF Viewer, PDF Embedder
Authenticated contributors can inject arbitrary scripts via shortcode attributes, potentially compromising editors or administrators who view the content.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-15098?
CVE-2026-15098 is a medium-severity cross-site scripting vulnerability in creativeinteractivemedia Real3D Flipbook – 3D FlipBook, PDF FlipBook, PDF Viewer, PDF Embedder, published on 19 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
The Real3D Flipbook Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'lightboxtext' shortcode attribute (and other unsanitized attributes handled by on_shortcode()) in versions up to, and including, 5.1.1. This is due to insufficient input sanitization and output escaping in the on_shortcode() and print_global_options() functions: shortcode attribute values are copied verbatim into $this->flipbook_options and then emitted via wp_json_encode() inside a <script type="application/json"> block without the JSON_HEX_TAG flag, allowing a literal </script> byte sequence in the attribute value to break out of the JSON script context. Because WordPress's shortcode_parse_atts() applies stripcslashes() to attribute values, an attacker can encode the breakout tag as \x3c/script\x3e\x3cscript\x3e…\x3c/script\x3e, which survives the wp_kses_post save-time filter applied to Contributor content (the escape bytes are safe text characters, not HTML tags) and is decoded to real angle brackets at render time. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user (typically an Editor or Administrator previewing/moderating the pending post) accesses an injected page.
Weakness: CWE-79
Which versions are affected by CVE-2026-15098?
How do I fix CVE-2026-15098?
No fix has been published for CVE-2026-15098 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-15098 being exploited?
There is no known exploitation of CVE-2026-15098 in the wild and no public exploit code.
Sources
Also known as GHSA-4vrv-fq2h-vgq6.