Athemes Addons For ElementorWordPress extension · Athemes
CVE-2024-51675
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 Syed Balkhi aThemes Addons for Elementor athemes-addons-for-elementor-lite allows DOM-Based XSS.This issue affects aThemes Addons for Elementor: from n/a through <= 1.0.7.
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 confidenceDOM-based Cross-Site Scripting (XSS) vulnerability in aThemes Addons for Elementor plugin allows attackers to inject malicious JavaScript through unsanitized input that gets incorporated into the DOM without proper neutralization. The vulnerability exists in the web page generation process of the plugin affecting versions up to and including 1.0.7.
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
Athemes Addons For ElementorWordPress extension
< 1.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify aThemes Addons for Elementor is installedLog in to WordPress admin, go to Plugins > Installed Plugins, and look for 'aThemes Addons for Elementor' in the listAffected if The plugin is installed and active in WordPress
-
Identify the installed version numberIn the Plugins list, find 'aThemes Addons for Elementor' and look under the plugin name for the version number, or click on the plugin to view detailsAffected if Version displayed is 1.0.7 or lower (any version below 1.0.8)
-
Confirm the plugin is used in page generationCheck if any Elementor pages or templates use widgets from this plugin by editing a page with Elementor and looking for aThemes widgets in the widget panelAffected if The plugin widgets are used to build pages on the site
You are affected if aThemes Addons for Elementor is installed with any version below 1.0.8 and that plugin or its widgets are used to generate pages on your site.
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 · scoped1.0.8
Update aThemes Addons for Elementor to the latest version beyond 1.0.7 to receive the security patch that properly sanitizes user input before DOM incorporation.
1.0.8
- Back up your WordPress site database and files before making any changes
- Navigate to WordPress Admin > Plugins > Installed Plugins
- Locate 'Athemes Addons for Elementor' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 1.0.8 if the automatic update is not showing
- After updating, clear any caching plugins or server-side caches
- Test the affected functionality to confirm the plugin is working correctly post-update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Athemes Addons For Elementor
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51675 — 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-2024-51675 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