# CVE-2025-2228: Information disclosure in Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates

> Authenticated contributors can extract usernames and passwords of users who register via a specific widget and open the notification email.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-5fh9-9r47-g22w

## What is CVE-2025-2228?

CVE-2025-2228 is a medium-severity vulnerability in cyberchimps Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates, published on 26 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-2228?

It affects 1 product.


Products: Cyberchimps Responsive Addons for Elementor.

## How do I fix CVE-2025-2228?

No fix has been published for CVE-2025-2228 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2228 being exploited?

There is no known exploitation of CVE-2025-2228 in the wild and no public exploit code.

## Other vulnerabilities in cyberchimps Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates

- [CVE-2024-13353](https://insights.sbomify.com/CVE-2024-13353/): Path traversal in Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates (high 8.8)
- [CVE-2025-54050](https://insights.sbomify.com/CVE-2025-54050/): WordPress Responsive Addons for Elementor plugin <= 1.7.3 - Cross Site Scripting (XSS) Vulnerability (medium 6.5)
- [CVE-2024-52358](https://insights.sbomify.com/CVE-2024-52358/): WordPress Responsive Addons for Elementor plugin <= 1.5.4 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2025-2225](https://insights.sbomify.com/CVE-2025-2225/): Cross-site scripting in Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2228 and fix it if it is affected.

What it is: CVE-2025-2228 is a medium-severity vulnerability in cyberchimps Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates, published on 26 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-2228 in the wild and no public exploit code.

Affected product: cyberchimps Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2228/ (Markdown: https://insights.sbomify.com/CVE-2025-2228/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2228
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2228
- OSV: https://osv.dev/vulnerability/CVE-2025-2228

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2228/
Summaries are generated and may contain mistakes; the official description above is the record.