CVE-2026-9601 · Package
NO FIX YET · SEE WHAT TO DO
The Stackable Page Builder Gutenberg Blocks plugin for WordPress does not sanitize input to its update_block_style endpoint, so stored scripts are saved. An attacker with contributor access can inject scripts that run in the browser of anyone who opens the injected page.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Stackable Page Builder Gutenberg Blocks plugin version 3.19.9 or earlier, where contributor-level or higher accounts exist. Sites without the plugin, or running a later version, are not affected according to the sources' version range.
Not affected if contributor-accounts-not-used, plugin-not-installed
Who cares self-hosted, stackable, wordpress
wp plugin get stackable-ultimate-gutenberg-blocks --field=version (plugin slug assumed; unknown if the sources do not confirm it)3.19.9 or earlier3.19.9 are affected; the sources do not state a fixed versionThe Stackable – Page Builder Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'update_block_style' endpoint in all versions up to, and including, 3.19.9 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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.