dbcve.org
Elementinvader Addons For ElementorWordPress extension · Elementinvader

CVE-2025-24618

HIGH · 8.8 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 1.3.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Missing Authorization vulnerability in Element Invader ElementInvader Addons for Elementor elementinvader-addons-for-elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ElementInvader Addons for Elementor: from n/a through <= 1.3.1.

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

Missing authorization vulnerability in Element Invader Addons for Elementor allows exploiting incorrectly configured access control security levels, potentially enabling unauthorized users to access privileged functionality or perform actions beyond their designated permissions.

MitigationImplement proper capability checks and role-based access control validation on all sensitive functions, AJAX endpoints, and admin pages to ensure users can only access functionality they're authorized for.

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

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate the ElementInvader plugin installation
    Check your WordPress wp-content/plugins directory for a folder named 'elementinvader' or similar variant containing 'elementinvader' in the name
    Affected if The plugin folder exists on the server
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually index.php or a file named elementinvader.php) and locate the 'Version' header in the plugin comment block
    Affected if The Version header shows a version number less than 1.3.2
  3. Compare against vulnerable version range
    Compare the discovered version number to the affected range: any version below 1.3.2 is vulnerable
    Affected if The installed version is 1.3.1, 1.3.0, 1.2.x, 1.1.x, 1.0.x, or any other version lower than 1.3.2
  4. Verify WordPress version is not mitigating factor
    This vulnerability is in the plugin itself and does not depend on WordPress core version; the broken access control exists regardless of WP version
    Affected if Plugin version is below 1.3.2 regardless of WordPress version

Your environment is affected if the ElementInvader Addons for Elementor plugin is installed and its version is lower than 1.3.2, as the missing authorization check exists in all prior versions.

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.2 or later
Fixed in 1.3.2
Interim mitigation

Implement proper capability checks and role-based access control validation on all sensitive functions, AJAX endpoints, and admin pages to ensure users can only access functionality they're authorized for.

Recommended fix High confidence

Elementinvader Addons For Elementor version 1.3.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Elementinvader Addons For Elementor' in the plugin list
  4. Check the current version number to confirm it is below 1.3.2
  5. If an update is available, click 'Update Now' to upgrade to version 1.3.2
  6. If no automatic update appears, manually download version 1.3.2 from the official WordPress plugin repository or the vendor's website
  7. Deactivate and delete the current plugin, then upload and activate version 1.3.2
  8. Verify the plugin is running version 1.3.2 after the update

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-24618 — 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-24618 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