EUVD-2026-39955
GHSA-qq5h-jpgc-p42f
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
PR:L reflects mandatory Contributor auth; S:C because XSS executes cross-origin in victim browsers; UI:N defensible for stored XSS where no additional victim interaction beyond page load is required.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
Lifecycle Timeline
2DescriptionCVE.org
The Page Builder by SiteOrigin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via panels_data Parameter in all versions up to, and including, 2.34.3 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 is possible because the nonce and edit_post capability checks enforced during save are both satisfied by Contributor-level users for their own posts, and the panels_data value is stored as post meta - outside the scope of WordPress's unfiltered_html carve-out - meaning no wp_kses fallback prevents the unsanitized WP_Widget_Custom_HTML content from being persisted and later rendered verbatim on the frontend.
AnalysisAI
Stored Cross-Site Scripting in the Page Builder by SiteOrigin WordPress plugin (all versions through 2.34.3) allows authenticated contributors to persist arbitrary JavaScript into post meta and execute it in any visitor's browser. The vulnerability bypasses WordPress's native content-filtering mechanisms because panels_data is stored as raw post meta rather than post content, placing it outside the scope of the unfiltered_html capability carve-out and the wp_kses fallback that would otherwise sanitize WP_Widget_Custom_HTML widget content. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low privilege bar (Contributor level) makes this a realistic threat on any multi-author or open-registration WordPress installation.
Technical ContextAI
CWE-79 (Improper Neutralization of Input During Web Page Generation - Cross-site Scripting) describes the root cause: user-supplied data is stored without sanitization and later rendered without escaping. In this case, the SiteOrigin Page Builder plugin accepts layout data through the panels_data POST parameter, processed in inc/admin.php (lines 236, 254, 1085). WordPress normally restricts raw HTML to users with the unfiltered_html capability, but panels_data is saved as post meta via wp_postmeta rather than post_content, which bypasses that protection entirely. The plugin's WP_Widget_Custom_HTML integration further compounds this: widget HTML written through the page builder is serialized into panels_data, persisted verbatim, and later rendered directly to the frontend by inc/renderer.php (line 950) without output escaping. The nonce and edit_post capability checks that gate the save routine are legitimately satisfied by any Contributor-level user editing their own posts, making the access control bypass structural rather than a simple logic flaw. Affected CPE: cpe:2.3:a:gpriday:page_builder_by_siteorigin:*:*:*:*:*:*:*:*.
RemediationAI
A fix commit has been landed in the plugin's SVN repository (changeset 3585987 at plugins.trac.wordpress.org); however, the exact patched release version number is not independently confirmed from the available reference data - administrators should update the plugin to the latest available version from the WordPress plugin directory and verify the installed version exceeds 2.34.3. If an immediate update is not possible, a viable compensating control is to restrict the Contributor role on sensitive WordPress installations: either prevent open contributor registration, audit existing contributor accounts, or temporarily revoke Contributor-level post-editing access until the patch is applied. Disabling the SiteOrigin Page Builder plugin entirely eliminates the attack surface but removes page builder functionality. Implementing a Web Application Firewall rule to block POST requests containing script-tag patterns in the panels_data parameter can reduce risk but may produce false positives on legitimate widget HTML. Each of these workarounds carries operational trade-offs and should be treated as temporary measures pending plugin update.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today