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

CVE-2026-11380

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-01
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 7 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 JetWidgets For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 1.0.21. This is due to insufficient output escaping and missing server-side validation of the Animated Box widget's animation_effect setting before it is rendered inside an HTML class attribute. This makes it possible for authenticated attackers, with author-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 JetWidgets For Elementor plugin fails to properly escape and validate the Animated Box widget's animation_effect setting before rendering it in an HTML class attribute. An authenticated attacker with author-level permissions can inject malicious JavaScript payloads into this setting, which gets stored and executed in the browsers of users viewing affected pages.

MitigationUpdate to a patched version of the plugin. Until then, restrict author-level access and manually review pages using the Animated Box widget for suspicious animation_effect values.

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. Verify JetWidgets For Elementor is installed
    Navigate to WordPress admin > Plugins and confirm JetWidgets For Elementor appears in the installed plugins list
    Affected if The plugin is present and no patched version is confirmed
  2. Check plugin version against known vulnerable releases
    In Plugins list, click on the plugin to view its version number, then compare to any patched version the vendor may have released
    Affected if The installed version predates the patched release and contains the vulnerability
  3. Identify pages using the Animated Box widget
    Search your WordPress database or use a site audit tool to find posts/pages containing the 'jet-animated-box' widget shortcode or block
    Affected if Any page content includes the Animated Box widget from this plugin
  4. Inspect animation_effect values in database
    Query the wp_postmeta table for meta_key containing 'animation_effect' or examine page content in the Elementor editor for the Animated Box widget settings
    Affected if Any animation_effect field contains unexpected JavaScript-like patterns such as <script, javascript:, onload=, or other HTML/script fragments
  5. Review author-level user accounts
    In WordPress admin > Users, list all users with Author role and verify which ones have edit access to pages containing the Animated Box widget
    Affected if Untrusted or unexpected author-level accounts exist with access to edit pages using this widget

Your environment is affected if the JetWidgets For Elementor plugin is installed with a vulnerable version and any page contains the Animated Box widget with a suspicious or unrecognized animation_effect value.

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

Update to a patched version of the plugin. Until then, restrict author-level access and manually review pages using the Animated Box widget for suspicious animation_effect values.

Recommended fix Moderate confidence

JetWidgets For Elementor version 1.0.22 or latest available release (after 1.0.21)

  1. 1. Log in to the WordPress admin dashboard with an account that has administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'JetWidgets For Elementor' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the Animated Box widget settings to ensure no malicious scripts were previously injected
  6. 6. Clear any caching mechanisms (site cache, CDN cache) to ensure the patched version is served

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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