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

CVE-2026-32352

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-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

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 Elementor Elementor Website Builder elementor allows DOM-Based XSS.This issue affects Elementor Website Builder: from n/a through <= 3.35.5.

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 Elementor Website Builder allows attackers to inject malicious JavaScript through improper handling of user-supplied input in the browser's DOM. The vulnerability exists in versions up to and including 3.35.5, where the application fails to sanitize input before using it in DOM manipulation operations.

MitigationUpdate Elementor Website Builder to the latest version (3.35.6 or later) which should contain the security patch. Until patched, warn users against clicking untrusted links containing Elementor URLs.

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. Identify installed Elementor version
    In WordPress admin, go to Elementor > About or check the plugins page to view the installed Elementor Website Builder version number
    Affected if The version displayed is 3.35.5 or lower (any version up to and including 3.35.5)
  2. Verify Elementor is active on the site
    Check WordPress plugins page to confirm Elementor Website Builder plugin is installed and activated
    Affected if Elementor plugin is active and version cannot be determined or is confirmed vulnerable
  3. Check WordPress access logs for XSS indicators
    Review web server access logs (Apache/Nginx) for requests containing script tags, javascript:, or other XSS payloads in URL parameters pointing to Elementor-related paths
    Affected if Suspicious XSS payload requests are found in logs targeting the Elementor endpoint
  4. Inspect browser console for DOM XSS evidence
    If you have admin access, navigate to a page edited with Elementor and open browser developer tools console to look for any unexpected script executions or errors
    Affected if Unexpected JavaScript execution occurs without explicit admin action
  5. Review Content Security Policy headers
    Check response headers from the site to see if Content-Security-Policy header is present and properly configured to block inline scripts
    Affected if CSP is missing or allows inline scripts, increasing exploitability
  6. Check for recent unauthorized changes
    Review Elementor editor history or WordPress revision logs for any unexpected page template or content changes made by unknown users
    Affected if Unauthorized modifications to pages or templates are found

The environment is affected if Elementor Website Builder version 3.35.5 or lower is installed, as this version contains the DOM-based XSS vulnerability in input handling.

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 Elementor Website Builder to the latest version (3.35.6 or later) which should contain the security patch. Until patched, warn users against clicking untrusted links containing Elementor URLs.

Recommended fix Moderate confidence

Elementor Website Builder 3.36.0 or later (latest stable release)

  1. Check your current Elementor Website Builder version in WordPress admin under Elementor > Settings > About
  2. If your version is 3.35.5 or lower, navigate to Dashboard > Updates in WordPress admin
  3. Update Elementor to the latest available version which contains the security fix for this DOM-based XSS vulnerability
  4. After updating, clear any caching plugins and verify the website still functions correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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