Atomic Edge analysis of CVE-2026-104676 (metadata-based): This vulnerability is an authenticated stored cross-site scripting (XSS) issue in the Zion Builder WordPress plugin, affecting all versions up to and including 3.6.17. An attacker with author-level privileges or higher can inject arbitrary web scripts into pages. When other users, including administrators, view the compromised page, the injected script executes in their browser. The CVSS score of 6.4 reflects a moderate severity with a network attack vector, low attack complexity, and low privileges required. The scope is changed because the vulnerable component (the plugin’s page rendering) impacts the browser of a user visiting the page. The patch status is unknown because no patched version is available.
Root Cause: Based on CWE-79 (Improper Neutralization of Input During Web Page Generation), the plugin fails to properly sanitize user input or escape output when rendering page content. Author-level users can typically create or edit posts and pages. The plugin likely provides custom fields, shortcodes, or builder elements that accept HTML or script content without adequate filtering. Atomic Edge analysis infers that the vulnerable code is in the plugin’s saving and rendering of custom page builder data. No source code diff is available, so this conclusion is inferred from the CWE and description, not confirmed from code.
Exploitation: An attacker with author access can create or modify a page using the Zion Builder interface. They inject a malicious script into a field that lacks proper sanitization, such as a text element, HTML block, or custom attribute. The script is stored in the WordPress database and executed when any user, including an administrator, visits the page. The exact parameter names and AJAX actions are unknown because no code is available. Atomic Edge research assumes the attack uses standard WordPress post editing or the plugin’s AJAX save mechanism, but the specific endpoint cannot be reliably determined from metadata alone.
Remediation: The fix must add proper input sanitization and output escaping for all user-supplied content, especially in the page builder’s save and render functions. WordPress provides functions like sanitize_text_field, wp_kses_post, and esc_html that developers should use. Since no patched version is available, users should disable the plugin or restrict author-level capabilities until a fix is released.
Impact: Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of other users’ browsers. This can lead to session hijacking, theft of credentials, or actions performed on behalf of the victim. Because the scope is changed, the attacker can potentially compromise the entire WordPress site by targeting administrators. The vulnerability requires author-level access, which limits the attacker pool but still poses a significant risk in multi-author sites.







