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

CVE-2026-57780

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 5 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Plugin Envision Envision Page Builder envision-page-builder allows DOM-Based XSS.This issue affects Envision Page Builder: from n/a through <= 0.22.

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 · moderate confidence

DOM-based Cross-site Scripting (XSS) vulnerability in the Envision Page Builder plugin allows attackers to inject malicious scripts through unsanitized input that gets dynamically inserted into the page's Document Object Model (DOM). This client-side XSS occurs when JavaScript processes data from untrusted sources without proper validation or encoding.

MitigationImplement proper input validation and output encoding when inserting data into the DOM; use safe DOM APIs and consider Content Security Policy (CSP) headers to mitigate XSS risks.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Envision Page Builder is installed
    Access your site's plugin management interface or inspect the plugin directory (wp-content/plugins/envision-page-builder or similar). Check for the presence of the Envision Page Builder plugin files.
    Affected if The plugin is installed on the site
  2. Identify the installed plugin version
    Look for a version declaration in the plugin's main PHP file (usually in the plugin header comments) or in a readme.txt file within the plugin directory. Alternatively, check the plugin admin interface for version information.
    Affected if The installed version matches or falls within the affected version range (compare your installed version to the affected ranges provided by official sources)
  3. Verify the plugin is active
    Check the WordPress admin dashboard under Plugins > Installed Plugins to confirm Envision Page Builder is activated, or query the site database wp_options table for active_plugins.
    Affected if The plugin is currently active and processing page content
  4. Identify DOM insertion points in the plugin
    Inspect the plugin's JavaScript files (typically in a js/ or assets/js/ subdirectory) for DOM manipulation functions such as innerHTML, outerHTML, insertAdjacentHTML, document.write, or jQuery's .html(), .append(), .prepend() methods that process dynamic content.
    Affected if The plugin JavaScript uses unsafe DOM insertion methods without apparent sanitization on user-controlled data
  5. Test for reflected user input in DOM
    Use browser developer tools to examine how the plugin handles input: create a test page with the builder, insert content containing HTML/script tags, save the page, then view the page source or use the Elements panel to see if the input is inserted as raw HTML into the DOM.
    Affected if User-supplied content is rendered as executable HTML in the DOM without encoding

You are affected if the Envision Page Builder plugin is installed, active, processes user input, and inserts that input into the DOM without sanitization or encoding.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding when inserting data into the DOM; use safe DOM APIs and consider Content Security Policy (CSP) headers to mitigate XSS risks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57780 — 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-57780 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