Kubio AI Page Builder

The supplied vector requires no attacker account. Attacker-controlled request input can be reflected into browser output without sufficient neutralization. When a victim interacts with the crafted request or response, script can execute under the site's origin. The export does not identify the endpoint, parameter, rendering function, output context or victim role. Victim interaction is required by the vector. The vector reports limited confidentiality impact, limited integrity impact, limited availability impact. Affected versions: <= 2.9.3. No fixed release is confirmed.

The Kubio AI Page Builder WordPress plugin before 2.9.3 does not limit its widening of the allowed HTML elements to the editor context, so the wider set is applied when filtering content submitted by unauthenticated users as well, allowing them to store markup which the Kubio AI Page Builder WordPress plugin before 2.9.3's own script later executes in the browser of any visitor, or of an administrator reviewing the still-unapproved submission. The authoritative export identifies the fixed release as 2.9.3.

The Kubio AI Page Builder WordPress plugin before 2.9.3 does not validate the URI scheme of a user-supplied value before outputting it as a link target, allowing users with the contributor role and above to store a payload which executes in the browser of anyone who follows the link, including an administrator previewing the unpublished submission. The authoritative export identifies the fixed release as 2.9.3.

The Kubio AI Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 2.9.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. No further endpoint or implementation detail is disclosed beyond the path described here. The official changelog confirms a matching fix in 2.9.3.

The Kubio AI Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via kubio/copyright Block Content in all versions up to, and including, 2.8.4 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 bypasses both the WordPress core kses-on-save filter and the plugin's own wp_kses_post() call, because entity-encoded script tags are treated as inert text by kses but are decoded into live HTML by the subsequent html_entity_decode() call in CopyrightBlock::render_template(). Entity decoding after HTML filtering reverses the protection; the export names the rendering function but not a dedicated request route. Affected versions reported by the CNA: <= 2.8.4.

Kubio AI Page Builder through 2.8.5 exposes an affected nonce to every user who can open the block editor. A Contributor can use that nonce to invoke insufficiently authorized Kubio operations that overwrite show_on_front, page_on_front, page_for_posts, navigation-menu assignments, template parts, and the Kubio global-data post.

Kubio AI Page Builder is affected by dangerous file upload. Exploitation requires an authenticated contributor account. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise. The published affected range is <= 2.7.2.

Kubio AI Page Builder is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is n/a through 2.7.0.

Kubio AI Page Builder is affected by a security weakness. Exploitation requires an authenticated subscriber account. The resulting impact depends on how the affected component exposes the vulnerable operation.

Kubio AI Page Builder is affected by filesystem traversal. The vulnerable path is reachable without authentication. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.

Kubio AI Page Builder is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.