CVE-2026-92746 jegstudio CVE debrief

Who should care

Defenders responsible for WordPress installations using the Gutenverse plugin should assess exposure and prioritize verification and potential updates. This includes operators managing WordPress environments, platform administrators, vulnerability management teams, and security teams that need to ensure the plugin is updated to prevent potential exploitation.

Why it matters

The Gutenverse plugin vulnerability allows authenticated attackers to inject arbitrary web scripts, which can lead to cross-site scripting attacks. Defenders should prioritize verifying and updating the plugin to prevent potential exploitation.

• Authenticated attackers with contributor-level access and above can inject arbitrary web scripts
• Injected scripts execute whenever a user accesses an injected page
• Defenders must verify and update the Gutenverse plugin to a fixed version, if available

Technical summary

The Gutenverse – WordPress Blocks, Page Builder & Site Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Post Comment Block 'suffixMain' Attribute in all versions up to, and including, 4.0.8 due to insufficient input sanitization and output escaping. 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 accesses an injected page.

Defensive priority

Defenders should prioritize verifying and updating the Gutenverse plugin to a fixed version, if available, and monitor for potential exploitation attempts.

Recommended defensive actions

• Verify and update the Gutenverse plugin to a fixed version, if available
• Monitor for potential exploitation attempts
• Implement additional security measures to detect and prevent cross-site scripting attacks
• 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 is due to insufficient input sanitization and output escaping in the Post Comment Block 'suffixMain' Attribute. The payload is stored inside a Gutenberg block delimiter comment rather than as a raw HTML tag, and is only rendered as exploitable HTML at the PHP render stage.

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.