Essential Addons For ElementorWordPress extension · Wpdeveloper
CVE-2025-24752
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPDeveloper Essential Addons for Elementor essential-addons-for-elementor-lite allows Reflected XSS.This issue affects Essential Addons for Elementor: from n/a through <= 6.0.14.
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 confidenceReflected XSS vulnerability in Essential Addons for Elementor lite plugin (versions <= 6.0.14) allows attackers to inject malicious JavaScript via unsanitized user input that gets reflected in web pages without proper encoding. The CVSS 6.1 indicates the attack requires user interaction (e.g., clicking a crafted link).
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
Essential Addons For ElementorWordPress extension
< 6.0.15CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > Essential Addons for Elementor. The version number is displayed below the plugin name.Affected if The displayed version is 6.0.14 or lower (e.g., 6.0.14, 6.0.13, 6.0.12, etc.)
-
Verify plugin statusIn the same plugins list, confirm whether Essential Addons for Elementor is currently activated.Affected if The plugin is active and the version is 6.0.14 or lower.
-
Identify reflected parameters in web pagesManually review URLs on pages where Essential Addons widgets are in use. Check for query parameters (e.g., ?search=, ?id=, ?filter=) that might reflect user input back into the HTML without encoding. Use browser developer tools or a proxy to inspect the page source.Affected if Any URL parameter value from Essential Addons elements appears unescaped in the page source (visible script tags, event handlers, or alert() calls if tested with harmless payloads).
-
Test for XSS via crafted URLWith authorization, simulate an attack by appending a test payload like ?test=<script>alert(1)</script> to URLs using Essential Addons widgets. Observe if the payload renders as plain text (safe) or executes/renders as HTML (vulnerable).Affected if The payload is rendered as HTML or executes JavaScript rather than being displayed as harmless text.
You are affected if Essential Addons for Elementor is active at version 6.0.14 or lower and any user-supplied input in the plugin's URL parameters is reflected into the page without HTML encoding.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.0.15
Upgrade to Essential Addons for Elementor version 6.0.15 or later which contains the security fix. If immediate patching is not possible, consider disabling the plugin or implementing WAF rules as a temporary workaround.
Essential Addons For Elementor version 6.0.15
- Backup your WordPress site before performing any updates
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'Essential Addons for Elementor' in the plugin list
- If an update is available, click 'Update Now' to install version 6.0.15
- Alternatively, you can update automatically via Dashboard > Updates
- After updating, verify the version number shows 6.0.15 in the plugins list to confirm the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Essential Addons For Elementor
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-24752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24752 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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