CVE-2026-8623 dearhive CVE debrief

Who should care

Defenders responsible for WordPress sites using the Dear Flipbook plugin should assess exposure and prioritize updating the plugin to prevent exploitation. This includes reviewing current plugin versions, identifying contributors with elevated access, and ensuring security measures are in place to monitor and mitigate potential threats.

Why it matters

The Dear Flipbook plugin for WordPress is vulnerable to Stored Cross-Site Scripting, allowing authenticated attackers to inject arbitrary web scripts. Defenders should prioritize verifying and updating the plugin to prevent exploitation.

• Authenticated attackers with contributor-level access can inject arbitrary web scripts.
• Injected scripts execute when a user accesses an injected page.
• Defenders must verify and update the Dear Flipbook plugin to prevent exploitation.
• Exposure requires verification from official sources.

Technical summary

The Dear Flipbook plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_content (class attribute of .dvcss element)' parameter in all versions up to, and including, 2.4.30. The payload is embedded as a Base64-encoded JSON object in a CSS class name on a Custom HTML block; the frontend parseCSSElements() function decodes it client-side with atob() and JSON.parse() and renders the logo property as raw HTML.

Defensive priority

Defenders should prioritize verifying and updating the Dear Flipbook plugin to prevent exploitation.

Recommended defensive actions

• Verify and update the Dear Flipbook plugin to the latest version.
• Restrict contributor-level access and above to trusted users.
• Monitor for suspicious activity on the WordPress site.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability allows authenticated attackers with contributor-level access to inject arbitrary web scripts via the 'post_content (class attribute of .dvcss element)' parameter. The payload is embedded as a Base64-encoded JSON object in a CSS class name on a Custom HTML block.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.