CVE-2026-115816 · Package
NO FIX YET
The Kubio AI Page Builder plugin for WordPress does not sanitize the review body field, so a logged-in subscriber can store script that runs in pages. The script runs for any user who opens an affected page after the review is approved.
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 Kubio AI Page Builder plugin at version 2.9.4 or earlier that use a Kubio-rendered single-product template. Exploitation needs a subscriber-level account and a review that is approved, either automatically or by an administrator. Sites without the plugin or without that template can skip it.
Not affected if no-kubio-post-content-template, plugin-not-installed, reviews-not-approved
Who cares kubio-ai-page-builder, woocommerce, wordpress
2.9.4 are affected.wp:post-content block.No fix yet, per the sources.
The Kubio AI Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment (review body)' parameter in all versions up to, and including, 2.9.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires the attacker's review containing the payload to be approved, either automatically (due to a previously approved review from the same account) or manually by an administrator, and the active single-product template must use a Kubio-rendered wp:post-content block.
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.