CVE-2026-39702
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 Wealcoder Animation Addons for Elementor animation-addons-for-elementor allows DOM-Based XSS.This issue affects Animation Addons for Elementor: from n/a through <= 2.6.1.
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 confidenceA DOM-based Cross-Site Scripting (XSS) vulnerability exists in the Wealcoder Animation Addons for Elementor WordPress plugin (versions <= 2.6.1). The vulnerability allows attackers to inject malicious JavaScript through unsanitized input that gets executed in the victim's browser via DOM manipulation. This is a client-side vulnerability where user-supplied data is directly used in page rendering without proper escaping.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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 plugin is installedCheck your WordPress plugins directory or Elementor plugins list for 'Wealcoder Animation Addons for Elementor'Affected if The plugin is installed and active in the WordPress environment
-
Determine installed versionAccess the plugin file header (typically in main plugin file) or WordPress plugin admin page to view the installed version numberAffected if Version cannot be determined or is within an affected range
-
Identify vulnerable featureInspect Elementor page builder where Wealcoder widgets are used; the DOM-based XSS typically occurs through widget settings that accept user input and render it directly to the page DOM without sanitizationAffected if User-controllable input fields in Wealcoder widgets accept and render unsanitized content to the browser
-
Check for malicious script executionUse browser developer tools to inspect the DOM and network activity; look for unexpected script tags or eval() calls originating from Wealcoder widget outputAffected if JavaScript executes from parameters that should have been neutralized by the plugin
You are affected if Wealcoder Animation Addons for Elementor is installed and user-supplied input from its widgets renders directly into the page DOM without proper sanitization.
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 · scopedUpdate to a patched version of Animation Addons for Elementor once available. Until then, restrict usage of the plugin or implement additional output encoding on the application layer. Review and sanitize any user-controlled data paths that interact with the plugin.
Latest version available from Wealcoder (vendor should confirm the specific fixed release above 2.6.1)
- 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins.
- 2. Locate 'Animation Addons for Elementor' by Wealcoder in the plugin list.
- 3. Check if an update is available for the plugin.
- 4. If an update is available, update the plugin to the latest version available from the vendor.
- 5. After updating, clear any caching mechanisms (site cache, CDN cache, browser cache) to ensure the fixed version is served.
- 6. Verify the fix by testing that the vulnerable parameter/input is no longer susceptible to XSS injection.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39702 — 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-2026-39702 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