Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as WordPress Contributor
-
DeliveryLoad block editor, extract nonce from window.kubioUtilsData
-
ExploitCraft AJAX request with harvested nonce targeting privileged Kubio actions
-
ExecutionOverwrite show_on_front and page_on_front options
-
PersistRewrite navigation menus and replace template parts
-
ImpactSite homepage and navigation defaced without admin credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid WordPress account with at minimum Contributor-level role on the target installation. The Kubio AI Page Builder plugin must be installed, active, and running version 2.8.5 or earlier. The attacker must be able to load the WordPress block editor (accessible to Contributors by default) in order to read the AJAX nonce from window.kubioUtilsData. Impact is bounded to integrity of front-page configuration (show_on_front, page_on_front, page_for_posts), primary navigation menu items, template parts, and the Kubio global-data post - no confidentiality or availability impact applies. Sites where all Contributor accounts belong to trusted personnel are not practically exploitable despite the vulnerability being present. |
| Impact | The CVSS 4.3 (Medium) score with vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N accurately reflects the constrained impact: integrity only, scoped to site configuration, requiring Contributor-level authentication. Despite the moderate score, real-world impact is more disruptive than I:L implies - homepage hijacking and navigation rewriting are visible, functional attacks that can undermine site trust and user experience. The AC:L rating is well-justified because the nonce is trivially harvestable simply by loading the block editor with a Contributor account. No KEV listing and no EPSS data were provided in the available intelligence, meaning systematic exploitation has not been confirmed by CISA. The Wordfence advisory and Trac changeset (revision 3633801) indicate a patch has been committed. Practical risk is bounded by the requirement for a registered Contributor account - sites with no untrusted Contributors face negligible exposure despite the flaw's presence. |
| Exploit ScenarioDerived | A registered Contributor on a WordPress site running Kubio AI Page Builder ≤2.8.5 logs in, loads the block editor to extract the nonce from window.kubioUtilsData, then sends crafted AJAX requests using that nonce to overwrite show_on_front and page_on_front options - redirecting the site homepage to an attacker-chosen page. The attacker can simultaneously rewrite the primary navigation menu and replace template parts, producing site-wide visual defacement without requiring Administrator or Editor credentials. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 16, 2026
Authorization bypass in Kubio AI Page Builder (WordPress plugin, all versions ≤2.8.5) enables any authenticated Contributor to overwrite front-page configuration options, rewrite primary navigation menus, replace template parts, and overwrite the plugin's global-data post. The plugin emits the AJAX nonce unconditionally into the JavaScript global window.kubioUtilsData for every user who can load the block editor - including Contributors - making the check_ajax_referer() call a non-functional authorization barrier. No public exploit identified at time of analysis, but the exploitation mechanism is fully documented in the Wordfence advisory and the vulnerable code paths are publicly visible in the WordPress plugin Trac repository.
RemediationAI
Update the Kubio AI Page Builder plugin to the latest available version beyond 2.8.5 immediately via the WordPress admin dashboard (Plugins > Updates); the upstream fix is confirmed in Trac changeset revision 3633801 at https://plugins.trac.wordpress.org/changeset?reponame=&old=3633801%40kubio&new=3633801%40kubio, though the specific patched release version number is not independently confirmed from the available data. As a compensating control if an immediate update is not possible, restrict the Contributor role to only fully trusted users - this eliminates the exploitation path entirely since Contributor-level access is a hard prerequisite. Alternatively, temporarily deactivating the Kubio AI Page Builder plugin prevents exploitation with the trade-off of disabling the page builder functionality. Do not rely on the existing check_ajax_referer() mechanism as a security control in unpatched versions, as the nonce it validates is exposed to all block editor users.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is rooted in CWE-862 (Missing Authorization): the plugin delegates authorization entirely to a nonce check via check_ajax_referer(), but the nonce itself is unconditionally embedded into window.kubioUtilsData for every user who loads the WordPress block editor - a role available to Contributors by default. This design conflates authenticity verification (nonce) with capability verification (role/permission), providing no actual access control boundary. The vulnerable logic is traceable to lib/src/Core/KubioFrontPageRevertNotice.php (lines 25 and 151) and lib/editor-assets.php (line 411), and affected AJAX handler registration is visible in lib/kubio-block-library.php (line 197). The CPE is cpe:2.3:a:extendthemes:kubio_ai_page_builder:*:*:*:*:*:*:*:* covering all versions through 2.8.5. The impacted WordPress options - show_on_front, page_on_front, page_for_posts - directly control site homepage behavior and can produce visible defacement-level changes.
Know when Kubio Ai Page Builder gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Contributor-level auth required (PR:L) to harvest nonce via block editor; impact limited to integrity of site configuration options (I:L), no confidentiality or availability effect.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Kubio Ai Page Builder
View allStored cross-site scripting in the Kubio AI Page Builder WordPress plugin before 2.9.3 lets unauthenticated attackers su
Stored cross-site scripting in the Kubio AI Page Builder WordPress plugin (all versions before 2.9.3) lets a user holdin
Unauthenticated stored cross-site scripting (XSS) in Kubio AI Page Builder up to and including version 2.9.2 allows remo
Reflected cross-site scripting in the WordPress plugin Kubio AI Page Builder (Extend Themes) affects every release throu
Stored cross-site scripting (XSS) in Extend Themes Kubio AI Page Builder through version 2.7.0 allows authenticated user
Stored cross-site scripting in the Kubio AI Page Builder plugin for WordPress (all versions up to and including 2.8.4) l
Kubio page builder plugin for WordPress allows authenticated attackers with Contributor-level access to upload arbitrary
EUVD-2026-59869
GHSA-mxh6-wmv3-9hg9
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB