dbcve.org
Elementinvader Addons For ElementorWordPress extension · Elementinvader

CVE-2025-24578

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 1.3.1 or later.
See remediation →
58/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 Element Invader ElementInvader Addons for Elementor elementinvader-addons-for-elementor allows DOM-Based XSS.This issue affects ElementInvader Addons for Elementor: from n/a through <= 1.3.0.

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 XSS vulnerability in the ElementInvader Addons for Elementor plugin (versions <= 1.3.0) allows attackers to inject malicious JavaScript code through user-controlled input that is processed by client-side JavaScript without proper sanitization or output encoding, enabling script execution in victims' browsers.

MitigationUpgrade to a patched version > 1.3.0. Alternatively, identify and sanitize all user inputs that flow into DOM operations using proper output encoding functions (e.g., textContent instead of innerHTML) and implement Content Security Policy headers.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Elementinvader Addons For ElementorWordPress extension
Affected:< 1.3.1

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate 'Elementinvader Addons For Elementor', and note the version number displayed. Alternatively, check the plugin header in the main PHP file (typically in /wp-content/plugins/elementinvader-addons-for-elementor/).
    Affected if The installed version is 1.3.0 or lower (less than 1.3.1).
  2. Identify vulnerable DOM manipulation code
    If you have access to the plugin files, search JavaScript source files for patterns like innerHTML being assigned user-controlled data (e.g., search for 'innerHTML =' combined with variables from URL parameters, form inputs, or AJAX responses).
    Affected if Any JavaScript code in the plugin uses innerHTML to render data derived from URL parameters, GET/POST inputs, or localStorage without sanitization.
  3. Audit custom Elementor widgets or templates
    If using custom widgets created with Elementinvader, inspect the widget settings for any text fields or dynamic content settings that render output. Check the widget's render() method in PHP and any associated JavaScript files for innerHTML usage.
    Affected if Custom widgets accept user input and render it via innerHTML in the frontend JavaScript.

You are affected if the installed version is below 1.3.1 OR if custom JavaScript in your Elementor setup uses innerHTML to render unsanitized user input from URL parameters or form submissions.

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
Upgrade available Upgrade to 1.3.1 or later
Fixed in 1.3.1
Interim mitigation

Upgrade to a patched version > 1.3.0. Alternatively, identify and sanitize all user inputs that flow into DOM operations using proper output encoding functions (e.g., textContent instead of innerHTML) and implement Content Security Policy headers.

Recommended fix Moderate confidence

1.3.1

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find 'ElementInvader Addons for Elementor' in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install version 1.3.1.
  5. 5. Alternatively, download ElementInvader Addons for Elementor version 1.3.1 from a trusted source and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is running version 1.3.1 in the Plugins section.
  7. 7. Test the affected functionality to ensure the DOM-Based XSS vulnerability is remediated and the plugin functions correctly.

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

Fix this in Elementinvader Addons For Elementor 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 the upgrade done

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-2025-24578 — 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-2025-24578 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