CVE-2026-104762 stellarwp CVE debrief

Who should care

Defenders responsible for WordPress sites using the Kadence Blocks — Page Builder Toolkit for Gutenberg Editor plugin should be aware of this vulnerability and take steps to verify the version in use and ensure that it is up to date.

Why it matters

Defenders should prioritize verifying the version of Kadence Blocks in use and ensuring that it is up to date, as well as monitoring for suspicious activity on their WordPress sites, as this vulnerability allows authenticated attackers to inject arbitrary web scripts.

• Authenticated attackers with author-level access and above can inject arbitrary web scripts in pages
• Injected scripts will execute whenever a user accesses an injected page
• This vulnerability requires verification of Kadence Blocks version and monitoring for suspicious activity

Technical summary

The Kadence Blocks — Page Builder Toolkit for Gutenberg Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Block Font Family Attribute in all versions up to, and including, 3.7.12 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability requires verification of Kadence Blocks version and monitoring for suspicious activity. Defenders should prioritize verifying the version of Kadence Blocks in use and ensuring that it is up to date, as well as monitoring for suspicious activity  

Defensive priority

Defenders should prioritize verifying the version of Kadence Blocks in use and ensuring that it is up to date, as well as monitoring for suspicious activity on their WordPress sites.

Recommended defensive actions

• Verify the version of Kadence Blocks in use and ensure that it is up to date
• Monitor for suspicious activity on WordPress sites
• Implement additional security measures to 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 CVE record and source item provide details on the vulnerability, including its description, affected versions, and CVSS score. However, there is limited information on the exploitability of the vulnerability and no known instances of exploitation.

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.