Kubio AI Page Builder <= 2.8.5 - Missing Authorization to Authenticated (Contributor+) Front-Page/Menu/Template Configuration Reversion via kubio_restore_front_page AJAX Action
Strategic Overview
- Status
- Patched in 2.8.6
- Affected Plugin
- Kubio AI Page Builder
- Affected Version
<= 2.8.5- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-16779
At a glance
CVE-2026-16779 is a medium-severity Missing Authorization vulnerability in the Kubio AI Page Builder WordPress plugin, affecting versions <= 2.8.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.8.6; sites on affected versions should update now. Disclosed August 2026, reported by Wordfence PRISM.
Vulnerability Overview
The Kubio AI Page Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.8.5. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to overwrite front-page configuration options (show_on_front, page_on_front, and page_for_posts), rewrite primary navigation menu items, replace template parts, and overwrite the Kubio global-data post. Although a nonce check via check_ajax_referer() is present, the nonce is unconditionally emitted into window.kubioUtilsData for every user who can load the block editor, making it harvestable by any Contributor and therefore an ineffective authorization barrier.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Kubio AI Page Builder <= 2.8.5 carries this weakness at check_ajax_referer(), and reaching it takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Kubio AI Page Builder the fix is 2.8.6: builds <= 2.8.5 are affected, anything from 2.8.6 onward is not.
Remediation
Update to version 2.8.6, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Kubio AI Page Builder 2.8.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Kubio AI Page Builder
- 9.8CVE-2025-2294: Kubio AI Page Builder <= 2.5.1 Local File Inclusion
CVE-2025-2294 - 6.4CVE-2026-34887: Kubio AI Page Builder <= 2.7.0 Stored XSS
CVE-2026-34887 - 6.4CVE-2024-39661: Kubio AI Page Builder <= 2.2.4 Stored XSS
CVE-2024-39661 - 6.1CVE-2024-13516: Kubio AI Page Builder <= 2.3.5 Reflected XSS
CVE-2024-13516
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C