dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-8444

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Animation Addons for Elementor – GSAP Powered Elementor Addons & Website Templates plugin for WordPress is vulnerable to DOM-Based Stored Cross-Site Scripting via the multiple parameters in all versions up to, and including, 2.6.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Animation Addons for Elementor plugin versions up to 2.6.7 contains a stored DOM-based XSS vulnerability due to insufficient input sanitization and output escaping on multiple parameters. Authenticated attackers with Contributor-level access can inject malicious JavaScript through these parameters, which executes when other users view the compromised pages.

MitigationUpdate the plugin to the latest version once available, or implement proper input sanitization and output escaping on all user-supplied parameters within the affected plugin code.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Animation Addons for Elementor plugin is installed and identify its version
    In WordPress admin, navigate to Plugins > Installed Plugins and locate 'Animation Addons for Elementor'. Note the version number displayed beneath the plugin name. Alternatively, access the plugin directory via file manager or SSH and open the main plugin PHP file to find the version constant defined near the top.
    Affected if The plugin is installed and the version is 2.6.7 or earlier
  2. Identify users with Contributor role
    In WordPress admin, go to Users > All Users and review the Role column for accounts marked as 'Contributor'. Alternatively, query the WordPress database: SELECT user_id FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%contributor%';
    Affected if At least one user with Contributor role exists in the system
  3. Examine content authored by Contributors for malicious scripts
    Review all posts and pages created by users with Contributor role. Inspect the content HTML for unexpected script tags, iframe elements, onload/onerror attributes, or other JavaScript that was not intentionally added. Use a database query to search for common XSS patterns: SELECT ID, post_title, post_content FROM wp_posts WHERE post_author IN (SELECT ID FROM wp_users WHERE user_login IN (SELECT user_id FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%contributor%')) AND (post_content LIKE '%<script%' OR post_content LIKE '%onerror=%' OR post_content LIKE '%javascript:%
    Affected if Any post or page content contains injected JavaScript that was not authored by an administrator

Your environment is affected if the Animation Addons for Elementor plugin version 2.6.7 or earlier is installed alongside at least one Contributor-level user account, as this combination enables stored XSS injection that executes when other users view the compromised pages.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version once available, or implement proper input sanitization and output escaping on all user-supplied parameters within the affected plugin code.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

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