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

CVE-2026-57620

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-26
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 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Tim Strifler Exclusive Addons Elementor allows Stored XSS. This issue affects Exclusive Addons Elementor: from n/a through 2.7.9.8.

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

This is a Stored Cross-Site Scripting (XSS) vulnerability in the Exclusive Addons Elementor WordPress plugin by Tim Strifler. The vulnerability stems from improper neutralization of user input during web page generation, allowing malicious scripts to be stored in the database and executed when other users view affected pages.

MitigationUpdate the Exclusive Addons Elementor plugin to the latest patched version. If no update is available, implement proper input validation and output escaping (using WordPress functions like esc_html(), esc_attr(), and wp_kses()) on all user-supplied data before rendering.

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. Verify Exclusive Addons Elementor plugin is installed
    Log into the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'Exclusive Addons Elementor' in the list. Confirm the plugin is active.
    Affected if The plugin is installed and active in WordPress.
  2. Identify the installed plugin version
    In the Plugins list, click on the plugin name to view details, or check the plugin header comment in /wp-content/plugins/exclusive-addons-elementor/includes/exclusive-addons-elementor.php for the 'Version' field.
    Affected if The installed version matches or falls within any vulnerable version range for this CVE.
  3. Determine if user input fields exist in plugin widgets
    Review the Exclusive Addons Elementor widgets available in the Elementor page builder. Identify any widgets that accept user-supplied text or content that gets stored and later rendered on the frontend.
    Affected if The plugin contains widgets or features that accept and store user input without proper sanitization.
  4. Inspect database for stored scripts in plugin-related options
    Query the wp_options table for entries with option_names containing 'exclusive_addons' or similar patterns. Use: SELECT * FROM wp_options WHERE option_name LIKE 'exclusive_addons%'; Check for any serialized or raw JavaScript content in option values.
    Affected if Malicious script tags or event handlers are found stored in plugin-related database entries.
  5. Review frontend pages using Exclusive Addons widgets
    Use the browser developer tools to inspect the HTML source of pages built with Exclusive Addons Elementor widgets. Look for unescaped HTML attributes, especially in text fields, heading widgets, or custom code widgets.
    Affected if User-supplied content is rendered without HTML escaping (e.g., <script> tags execute or event handlers like onload= are present in the rendered HTML).

Your environment is affected if the Exclusive Addons Elementor plugin is active, contains any vulnerable version, and exposes widgets or features that accept user input which gets stored and rendered without proper output escaping.

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

Update the Exclusive Addons Elementor plugin to the latest patched version. If no update is available, implement proper input validation and output escaping (using WordPress functions like esc_html(), esc_attr(), and wp_kses()) on all user-supplied data before rendering.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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