WordPress - Kubio AI Website Builder DoS

Medium

Synopsis

The REST endpoint `GET /wp-json/kubio/v1/enable-theme` passes the client-supplied `name` parameter directly and without validation into WordPress core's `switch_theme()`:

// lib/api/colibri.php
function kubio_enable_theme( WP_REST_Request $data ) {
   switch_theme( $data['name'] );                       // <-- no type/value validation
   return wp_send_json( array( 'switched' => $data['name'] ) );
}

Because `$data['name']` is not type-checked, an authorized request can supply `name` as an array instead of a string. `switch_theme()` persists that value into the `stylesheet` / `template` options, where it is stored as a serialized array. On the next page load WordPress core calls `get_stylesheet()` which is typed to return a string and fatals with a `TypeError` during theme bootstrap, taking the entire site down.

The failure is persistent, the corrupted option is reloaded on every request.

Solution

Upgrade to Kubio AI Website Builder Plugin for WordPress version 2.9.1 or later.

Additional References

https://wordpress.org/plugins/kubio/

Disclosure Timeline

July 22 2026 - Security Contact Request
July 23 2026 - Vendor acknowledge
August 28 2026 - Ask if the fix has been released
August 31 2026 - The vendor has indicated that this has been fixed in version 2.9.1

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]