dbcve.org
Elementinvader Addons For ElementorWordPress extension · Elementinvader

CVE-2024-38705

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-20
Fix available
A fix is available. Upgrade to 1.2.5 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 (XSS or 'Cross-site Scripting') vulnerability in ElementInvader ElementInvader Addons for Elementor allows Stored XSS.This issue affects ElementInvader Addons for Elementor: from n/a through 1.2.4.

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 · high confidence

A Stored XSS vulnerability exists in ElementInvader Addons for Elementor (versions up to 1.2.4) where user-supplied input is not properly sanitized before being rendered in web pages. This allows authenticated attackers to inject malicious JavaScript that executes in browsers of users viewing the affected content.

MitigationUpdate ElementInvader Addons for Elementor to the latest patched version. If no update is available, implement server-side input validation and output encoding on all user input fields within the plugin.

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

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. Locate the installed version of ElementInvader Addons for Elementor
    In WordPress admin, go to Plugins > Installed Plugins and find 'Elementinvader Addons For Elementor' to view the version number. Alternatively, check the main plugin file (typically /wp-content/plugins/elementinvader-addons-for-elementor/elementinvader-addons.php) for the 'Version' header in the plugin comment block.
    Affected if The displayed version number is lower than 1.2.5 (for example, 1.2.4, 1.2.3, 1.0.0, etc.).
  2. Identify plugin components that accept user input
    Review the plugin settings pages and any public-facing widgets or shortcodes provided by ElementInvader Addons. Look for input fields where site administrators or content editors can enter text, URLs, HTML, or other data that gets stored and displayed on the site.
    Affected if The plugin contains any form fields, settings inputs, or content areas where user-supplied data is saved to the database and later rendered on pages without additional sanitization.
  3. Inspect stored content for unescaped output
    Examine pages on the site that render content created through the plugin. View the page source in a browser and check if user-provided text appears as raw HTML or with unescaped characters (for example, <script> tags appearing literally instead of as &lt;script&gt;).
    Affected if User input is rendered directly in HTML without proper encoding, allowing injected JavaScript to execute when the page is viewed.

You are affected if the installed version is below 1.2.5 AND the plugin is actively used with any user input functionality where data is stored and displayed on the site.

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.5 or later
Fixed in 1.2.5
Interim mitigation

Update ElementInvader Addons for Elementor to the latest patched version. If no update is available, implement server-side input validation and output encoding on all user input fields within the plugin.

Recommended fix High confidence

1.2.5

  1. 1. Log in to the WordPress admin dashboard where ElementInvader Addons for Elementor is installed
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'ElementInvader Addons for Elementor' in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually upload/install version 1.2.5
  5. 5. After updating, verify the plugin version shows 1.2.5
  6. 6. Clear any caching plugins or server-side caches to ensure the fix is fully applied

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 / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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