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

CVE-2026-9243

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-29
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 Plus Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'carousel_direction' parameter of the Carousel Anything widget in versions up to, and including, 6.4.15 This is due to insufficient output escaping in the render() function, where the carousel_direction value is placed into an unquoted HTML attribute (dir=) allowing attribute injection despite the use of esc_attr(). 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 Plus Addons for Elementor plugin (versions up to 6.4.15) contains a stored XSS vulnerability in the Carousel Anything widget's render() function. Although esc_attr() is used, the carousel_direction parameter is placed into an unquoted HTML attribute (dir=), allowing attribute injection via crafted input that breaks out of the attribute context.

MitigationUpdate the Plus Addons for Elementor plugin to a version beyond 6.4.15 that includes proper attribute quoting and escaping for the carousel_direction parameter, or apply a code fix that ensures the dir attribute value is properly quoted and escaped.

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. Identify plugin installation and version
    Check the installed version of Plus Addons for Elementor plugin. In WordPress admin, go to Plugins > Installed Plugins and look for 'Plus Addons for Elementor' to see the version number. Alternatively, check the main plugin file header at wp-content/plugins/the-plus-addons-for-elementor/classes/the-plus-elementor.php or use wp-cli: wp plugin list --name='the-plus-addons-for-elementor'
    Affected if The plugin version is 6.4.15 or lower
  2. Locate Carousel Anything widget usage
    Search your WordPress pages, posts, or templates for instances of the Carousel Anything widget. In Elementor editor, look for the widget under 'The Plus Addons' category. Check page content for [plus-carousel-any] shortcodes or inspect Elementor template files for carousel widget inclusions.
    Affected if The Carousel Anything widget is actively used in any published content
  3. Inspect rendered HTML for unquoted dir attribute
    View the source HTML of a page containing a Carousel Anything widget. Look for the dir= attribute in carousel container elements. The vulnerability exists when dir= appears without quotes around its value, for example: <div class="plus-carousel" dir=right> instead of <div class="plus-carousel" dir="right">. Use browser dev tools or view-source to examine the rendered markup.
    Affected if The rendered carousel HTML contains an unquoted dir= attribute that could be broken out of using a payload like 'dir=x onload=alert(1)'

You are affected if the Plus Addons for Elementor plugin version is 6.4.15 or lower and a Carousel Anything widget with a manipulatable carousel_direction setting is rendering an unquoted dir attribute in the HTML output.

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 the Plus Addons for Elementor plugin to a version beyond 6.4.15 that includes proper attribute quoting and escaping for the carousel_direction parameter, or apply a code fix that ensures the dir attribute value is properly quoted and escaped.

Recommended fix Moderate confidence

Latest version of Plus Addons for Elementor (version 6.4.16 or higher)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Plus Addons for Elementor' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. After updating, clear any caching plugins or server-side caches
  6. 6. Verify the Carousel Anything widget functionality works correctly after the update

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-9243 — 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-9243 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