dbcve.org
Responsive Addons For ElementorWordPress extension · Cyberchimps

CVE-2025-2228

MEDIUM · 5.7 CVSS v3.1 Published 2025-03-26
Fix available
A fix is available. Upgrade to 1.6.9 or later.
See remediation →
61/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
The Responsive Addons for Elementor – Free Elementor Addons Plugin and Elementor Templates plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.6.8 the 'register_user' function. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive data including usernames and passwords of any users who register via the Edit Login | Registration Form widget, as long as that user opens the email notification for successful registration.

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

The Responsive Addons for Elementor plugin versions up to 1.6.8 contains a sensitive information exposure vulnerability in its 'register_user' function. Authenticated attackers with Contributor-level access can extract usernames and passwords of users who register through the Edit Login | Registration Form widget, as this sensitive data is exposed in registration email notifications.

MitigationUpdate the Responsive Addons for Elementor plugin to version 1.6.9 or later to remediate this vulnerability. Additionally, consider resetting passwords for any users who registered via the affected widget during the vulnerable period.

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

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/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 the installed plugin version
    In WordPress admin, go to Plugins > Responsive Addons for Elementor and view the version number, or check the plugin header in the main plugin file
    Affected if The installed version is lower than 1.6.9 (versions 1.6.8 and below are affected)
  2. Identify use of the Login | Registration Form widget
    Search pages and posts for the Edit Login | Registration Form widget from Responsive Addons for Elementor, or review the site's widget inventory
    Affected if The Registration Form widget is present and enabled on the site
  3. Review WordPress user roles
    Check the Users list in WordPress admin for any accounts with Contributor-level access that you do not recognize or that were created recently
    Affected if There are untrusted or unexpected Contributor-level accounts on the site
  4. Examine registration email notifications
    If you have access to email logs or can review sent emails, check registration notification emails for the presence of plaintext passwords
    Affected if Registration emails contain plaintext passwords instead of only reset links

You are affected if the plugin version is below 1.6.9 AND the Login | Registration Form widget is in use on your site, allowing any Contributor-level user to access registration data.

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.9 or later
Fixed in 1.6.9
Interim mitigation

Update the Responsive Addons for Elementor plugin to version 1.6.9 or later to remediate this vulnerability. Additionally, consider resetting passwords for any users who registered via the affected widget during the vulnerable period.

Recommended fix High confidence

1.6.9 or later

  1. 1. Navigate to your WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find "Responsive Addons For Elementor" in the plugin list
  4. 4. Click "Update now" if an update is available, or manually update to version 1.6.9 or later
  5. 5. Verify the plugin version shows 1.6.9 or higher after updating

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

Fix this in Responsive Addons For Elementor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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