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

CVE-2026-15299

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-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 6 weeks old

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 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'weather_style' and 'move_direction' parameters of the Weather widget in all versions up to, and including, 2.6.3. This is due to insufficient output escaping in the Weather widget's render() function at widgets/weather.php:1246, where both settings values are placed into an HTML class attribute without esc_attr(). Elementor does not server-side validate widget SELECT control values against allowed options on save, so an authenticated attacker with Contributor-level access or above can submit a crafted save_builder AJAX request storing arbitrary values in the _elementor_data post meta. The stored payload renders unescaped on every frontend visit to the affected page (the Weather widget requires an OpenWeatherMap API key to reach the vulnerable output, which is the normal operational state for sites using this widget).

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 for WordPress is vulnerable to Stored Cross-Site Scripting in the Weather widget. Authenticated attackers with Contributor-level or higher access can inject arbitrary JavaScript via crafted save_builder AJAX requests that store malicious values in the _elementor_data post meta for the weather_style and move_direction parameters. These values render without escaping in HTML class attributes at widgets/weather.php:1246, causing the XSS to execute on every frontend visit.

MitigationUpgrade to the latest version of Animation Addons for Elementor which includes proper output escaping (esc_attr()) for the weather_style and move_direction parameters in the Weather widget render function. Alternatively, manually add esc_attr() wrapping around these parameters at line 1246 of widgets/weather.php.

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. Confirm Animation Addons for Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Animation Addons for Elementor'. Note the installed version number.
    Affected if The plugin is installed and the version falls within the vulnerable range before the fix was applied.
  2. Check for Weather widget usage
    Query the WordPress database for posts containing the Weather widget configuration in _elementor_data meta: SELECT post_id FROM wp_postmeta WHERE meta_key = '_elementor_data' AND meta_value LIKE '%"widgetType":"animation-addons-weather%';
    Affected if Any post or page uses the Weather widget from this plugin, creating potential storage of malicious values.
  3. Inspect weather widget rendering code
    Open widgets/weather.php in the plugin directory and locate line 1246 (or the render function for weather_style and move_direction). Check if esc_attr() is used when outputting these values in HTML class attributes.
    Affected if The code directly outputs weather_style or move_direction parameters into HTML class attributes without esc_attr() wrapping, indicating the vulnerability is present.
  4. Examine stored _elementor_data for suspicious values
    Query the _elementor_data meta for the weather widget and inspect the weather_style and move_direction values: SELECT meta_value FROM wp_postmeta WHERE meta_key = '_elementor_data' AND meta_value LIKE '%animation-addons-weather%'. Look for quotes, javascript:, or other XSS payloads in those fields.
    Affected if The stored values contain unescaped characters (quotes, angle brackets, or script keywords) in weather_style or move_direction parameters.

A user is affected if they have Animation Addons for Elementor installed with a vulnerable version, the Weather widget is in use, and the rendering code lacks esc_attr() escaping for weather_style and move_direction parameters in HTML class attributes.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of Animation Addons for Elementor which includes proper output escaping (esc_attr()) for the weather_style and move_direction parameters in the Weather widget render function. Alternatively, manually add esc_attr() wrapping around these parameters at line 1246 of widgets/weather.php.

Recommended fix Moderate confidence

Latest version after 2.6.3 (check WordPress plugin repository for current release)

  1. 1. Update the Animation Addons for Elementor plugin to the latest available version from the WordPress plugin repository
  2. 2. Navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. 3. Locate Animation Addons for Elementor and click Update Now if an update is available
  4. 4. After updating, clear any caching plugins or server-side caches
  5. 5. Verify the Weather widget still functions correctly with the OpenWeatherMap API key
Caveat Minimal risk - this is a security patch; verify Weather widget functionality with your OpenWeatherMap API key after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

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

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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