dbcve.org
Responsive Addons For ElementorWordPress extension · Cyberchimps

CVE-2025-54050

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-16
Fix available
A fix is available. Upgrade to 1.7.4 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 Stored XSS.This issue affects Responsive Addons for Elementor: from n/a through <= 1.7.3.

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 Responsive Addons for Elementor plugin allows attackers to inject malicious JavaScript through plugin settings fields that are rendered without proper sanitization in Elementor page builder pages, potentially affecting site administrators and frontend users.

MitigationUpdate to the latest patched version when released. Until then, restrict administrative access and implement additional output escaping on the server side for plugin-related content.

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

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. Verify the plugin is installed
    Check your WordPress plugins directory or use WP-CLI: wp plugin list --name='responsive-addons-for-elementor' to confirm Cyberchimps Responsive Addons For Elementor is present.
    Affected if The plugin is installed and active in WordPress.
  2. Check the installed version
    View the plugin file header (usually in readme.txt or the main plugin PHP file) or use: wp plugin get responsive-addons-for-elementor to retrieve the version number.
    Affected if The installed version is earlier than 1.7.4.
  3. Confirm Elementor page builder is active
    Check if Elementor website builder plugin is installed and active on the same WordPress site, since the XSS specifically affects pages built with Elementor.
    Affected if Elementor is active and the vulnerable plugin settings are accessible.
  4. Identify if plugin settings have been configured
    Review the plugin settings in WordPress admin under Responsive Addons for Elementor settings panel. The vulnerability exists in settings fields, so settings must exist for the XSS to be stored.
    Affected if Plugin settings fields have been populated and saved in the database.

A user is affected if Cyberchimps Responsive Addons For Elementor version is below 1.7.4, Elementor is active, and the plugin settings have been configured with user-supplied content that could contain malicious scripts.

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.7.4 or later
Fixed in 1.7.4
Interim mitigation

Update to the latest patched version when released. Until then, restrict administrative access and implement additional output escaping on the server side for plugin-related content.

Recommended fix Moderate confidence

Responsive Addons for Elementor 1.7.4

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Responsive Addons for Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 1.7.4 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  5. Verify the plugin is updated to version 1.7.4 or later
  6. Clear any caching plugins or server-side caches to ensure the fix takes effect

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

Fix this in Responsive Addons For Elementor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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