dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-13295

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Page Builder by SiteOrigin plugin fails to sanitize the panels_data parameter and escape output when rendering WP_Widget_Custom_HTML content. Authenticated users with Contributor-level access can inject malicious JavaScript via unsanitized custom HTML widgets that persist as post meta and execute on page access.

MitigationUpdate the plugin to a version beyond 2.34.3 that implements proper input sanitization (wp_kses fallback) and output escaping for panels_data and WP_Widget_Custom_HTML content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SiteOrigin Page Builder is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Page Builder by SiteOrigin'. Note the installed version number.
    Affected if The plugin is installed and the version is at or below the last vulnerable release before sanitization was implemented.
  2. Identify posts/pages using Page Builder with Custom HTML
    Query the wp_postmeta table for rows where meta_key contains 'panels_data' and meta_value includes 'type":"custom_html" or similar Custom HTML widget markers.
    Affected if The site contains post meta entries with Custom HTML widgets that may contain unsanitized script content.
  3. Inspect stored panels_data for unsanitized JavaScript
    Examine the raw meta_value of panels_data entries. Look for <script> tags, javascript: URIs, or HTML event attributes (onclick, onerror, onload, etc.) that are not escaped or wrapped in wp_kses-safe entities.
    Affected if The stored panels_data contains raw script tags or event handlers that would execute if rendered without additional sanitization.
  4. Verify Contributor role has Page Builder edit access
    Check if users with Contributor role can access the Page Builder editor. Go to Users > Roles in WordPress admin, or inspect capability mappings for the contributor role.
    Affected if Contributors can create or edit Page Builder layouts containing Custom HTML widgets.

A user is affected if the SiteOrigin Page Builder plugin is installed with a version lacking proper sanitization, and the site contains Contributor-accessible Custom HTML widgets in post meta that render unescaped script content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 2.34.3 that implements proper input sanitization (wp_kses fallback) and output escaping for panels_data and WP_Widget_Custom_HTML content.

Recommended fix Moderate confidence

Page Builder by SiteOrigin version 2.34.4 or latest stable release

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Page Builder by SiteOrigin' plugin
  4. Check the current installed version
  5. Navigate to Plugins > Add New > Upload (or check for updates)
  6. Update to the latest available version (verify version is 2.34.4 or higher)
  7. Test that the page builder functionality works correctly after update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13295 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13295 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data