dbcve.org
Responsive Addons For ElementorWordPress extension · Cyberchimps

CVE-2024-52358

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-11
Fix available
A fix is available. Upgrade to 1.6.0 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 CyberChimps Responsive Addons for Elementor responsive-addons-for-elementor allows DOM-Based XSS.This issue affects Responsive Addons for Elementor: from n/a through <= 1.5.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 · moderate confidence

A DOM-Based Cross-Site Scripting (XSS) vulnerability exists in the CyberChimps Responsive Addons for Elementor WordPress plugin (versions up to and including 1.5.4). The vulnerability allows attackers to inject malicious scripts into web pages generated by the plugin through improper neutralization of user-supplied input in the DOM.

MitigationUpgrade to a patched version of Responsive Addons for Elementor that addresses this vulnerability, or implement proper input sanitization and output encoding for all user-controlled data rendered in the DOM.

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
Responsive Addons For ElementorWordPress extension
Affected:< 1.6.0

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
    Locate the CyberChimps Responsive Addons for Elementor plugin in your WordPress installation under wp-content/plugins/ directory, or check via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin is present in the plugins directory or listed in WordPress admin plugins list
  2. Identify installed version
    Check the plugin version number in the plugin header of the main PHP file (usually responsive-addons-for-elementor.php) or use wp-cli command: wp plugin list --name='responsive-addons-for-elementor'
    Affected if The version shown is 1.5.4 or lower (any version below 1.6.0)
  3. Verify plugin is active
    Check through WordPress admin that the plugin status shows as 'Active', or query the database: SELECT * FROM wp_options WHERE option_name LIKE 'active_plugins'
    Affected if The plugin appears in the active plugins list and is currently enabled on the site
  4. Assess DOM input exposure
    Review pages using the plugin's widgets or elements that accept or display user-supplied content (such as custom HTML widgets, text fields, or dynamic content areas). Inspect the page source to see if user input is being directly inserted into the DOM without proper encoding
    Affected if The plugin renders user-controlled data directly into HTML/JavaScript on the frontend without sanitization

You are affected if the CyberChimps Responsive Addons for Elementor plugin is installed, active, and running version 1.5.4 or below, with any of its frontend widgets processing unsanitized user 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.6.0 or later
Fixed in 1.6.0
Interim mitigation

Upgrade to a patched version of Responsive Addons for Elementor that addresses this vulnerability, or implement proper input sanitization and output encoding for all user-controlled data rendered in the DOM.

Recommended fix High confidence

Responsive Addons for Elementor version 1.6.0 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. Find 'Responsive Addons for Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.6.0 of the plugin
  5. Verify the plugin has been updated to version 1.6.0 or higher
  6. Test that the Elementor widgets using Responsive Addons are functioning correctly

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

Fix this in Responsive Addons For Elementor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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