dbcve.org
Elementor Addon ElementsWordPress extension · Webtechstreet

CVE-2024-30422

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-28
Fix available
A fix is available. Upgrade to 1.13.2 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 WPVibes Elementor Addon Elements addon-elements-for-elementor-page-builder.This issue affects Elementor Addon Elements: from n/a through <= 1.13.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

This is a stored Cross-site Scripting (XSS) vulnerability in the WPVibes Elementor Addon Elements WordPress plugin (addon-elements-for-elementor-page-builder). The vulnerability exists in versions through 1.13.1, where the plugin fails to properly sanitize user input during web page generation, allowing attackers to inject malicious JavaScript code that executes in the browsers of users viewing affected pages.

MitigationUpdate the plugin to the latest version once the security patch is released. In the interim, implement Content Security Policy (CSP) headers and ensure all user-supplied input is properly sanitized before output.

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
Elementor Addon ElementsWordPress extension
Affected:< 1.13.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
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 the Elementor Addon Elements plugin is installed
    Log in to WordPress admin, go to Plugins > Installed Plugins, and look for 'Elementor Addon Elements' (also known as 'addon-elements-for-elementor-page-builder' or 'WPVibes Elementor Addon Elements'). Alternatively, check the /wp-content/plugins/ directory for a folder named 'addon-elements-for-elementor-page-builder'.
    Affected if The plugin is installed and active in WordPress
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find the Elementor Addon Elements plugin, and note the version number displayed below the plugin name. Alternatively, check the main plugin file (usually addon-elements-for-elementor-page-builder.php) for the 'Version' header in the plugin metadata.
    Affected if The version number is lower than 1.13.2 (versions through 1.13.1 are affected)
  3. Verify the vulnerability is exploitable
    This is a stored XSS, so the flaw only applies when the plugin is actively rendering pages with user-supplied input. Check any Elementor pages or posts that use the addon elements (such as form elements, content widgets, or any element that accepts and displays user input).
    Affected if The plugin is active and rendering pages that accept user input through Elementor addon elements

You are affected if the Elementor Addon Elements plugin is installed with a version lower than 1.13.2 and is actively used to render pages containing user-supplied input.

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.13.2 or later
Fixed in 1.13.2
Interim mitigation

Update the plugin to the latest version once the security patch is released. In the interim, implement Content Security Policy (CSP) headers and ensure all user-supplied input is properly sanitized before output.

Recommended fix High confidence

Elementor Addon Elements version 1.13.2

  1. 1. Create a full backup of your WordPress site before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'Elementor Addon Elements' (addon-elements-for-elementor-page-builder)
  5. 5. If an update is available, click 'Update Now' to update to version 1.13.2
  6. 6. Alternatively, download version 1.13.2 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the plugin version shows 1.13.2 in the plugins list
  8. 8. Test that Elementor page builder functionality continues to work correctly
Caveat Minor plugin version updates typically do not introduce breaking changes; ensure your Elementor and WordPress core versions are compatible

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

Fix this in Elementor Addon Elements Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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