dbcve.org
Elementinvader Addons For ElementorWordPress extension · Elementinvader

CVE-2024-47630

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-05
Fix available
A fix is available. Upgrade to 1.2.8 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 Stored XSS.This issue affects ElementInvader Addons for Elementor: from n/a through <= 1.2.7.

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

Stored XSS vulnerability in Element Invader Addons for Elementor plugin (versions <=1.2.7) allows authenticated attackers to inject malicious JavaScript through unsanitized input fields, which then executes when other users view affected pages in the Elementor page builder.

MitigationUpdate Element Invader Addons for Elementor to the latest patched version. If no patch is available, disable the plugin until a fix is released and audit the site for existing injected scripts.

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.2.8

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. Check if Element Invader Addons for Elementor is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Elementinvader Addons For Elementor' or check the plugin directory wp-content/plugins/element-invader for the main plugin file
    Affected if The plugin is present on the system
  2. Verify the installed version number
    In WordPress admin > Plugins, find the plugin and view the version number under the plugin name, or read the 'readme.txt' or 'element-invader.php' main file in the plugin directory to find the Version header
    Affected if Version is 1.2.7 or lower (anything below 1.2.8)
  3. Confirm the plugin is active
    Check the status column in WordPress admin > Plugins > Installed Plugins - the plugin must be active for the vulnerability to be exploitable
    Affected if Plugin shows as 'Active'
  4. Audit for injected malicious scripts in Elementor content
    Search WordPress database tables (wp_posts, wp_postmeta) for script tags, javascript:, or onload/onerror event handlers within content created or edited with Elementor, particularly widgets provided by Element Invader
    Affected if Suspicious script tags or event handlers are found stored in post content or meta
  5. Review WordPress user accounts with Elementor editor access
    Check Users > All Users in WordPress admin, looking for users with Elementor editor role or contributors/authors who have access to edit pages using Elementor
    Affected if Multiple users have Elementor editing capabilities and one account may be compromised

You are affected if Element Invader Addons for Elementor is installed, active, and running version 1.2.7 or lower, or if suspicious script injections are found in Elementor-stored 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
Upgrade available Upgrade to 1.2.8 or later
Fixed in 1.2.8
Interim mitigation

Update Element Invader Addons for Elementor to the latest patched version. If no patch is available, disable the plugin until a fix is released and audit the site for existing injected scripts.

Recommended fix High confidence

1.2.8

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'ElementInvader Addons for Elementor' in the plugin list
  5. 5. If an update is available, click 'Update Now' to upgrade to version 1.2.8 or later
  6. 6. Alternatively, download version 1.2.8 from a trusted source and upload it via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the plugin version shows 1.2.8 or higher
  8. 8. Test the affected functionality to ensure the plugin continues to work correctly
Caveat Minor plugin version upgrade; unlikely to have breaking changes, but test in staging first

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

Fix this in Elementinvader Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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