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

CVE-2026-5243

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-14
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 The Plus Addons for Elementor – Addons for Elementor, Page Templates, Widgets, Mega Menu, WooCommerce plugin for WordPress is vulnerable to stored cross-site scripting via the `menu_hover_click` parameter of the Navigation Menu Lite widget in all versions up to, and including, 6.4.11 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 Plus Addons for Elementor plugin contains a stored XSS vulnerability in the Navigation Menu Lite widget's menu_hover_click parameter. Authenticated attackers with contributor-level permissions can inject arbitrary JavaScript through insufficient input sanitization, which persists in the database and executes when other users access affected pages.

MitigationUpdate the plugin to a version beyond 6.4.11 which contains proper input sanitization and output escaping for the affected parameter.

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 installed plugin version
    Navigate to WordPress dashboard > Plugins > Plus Addons for Elementor and note the version number displayed, or use wp-cli: wp plugin list --name='plus-addons-for-elementor'
    Affected if Version is 6.4.11 or earlier (the vulnerability is patched in versions beyond 6.4.11)
  2. Identify Navigation Menu Lite widget usage
    Search WordPress pages/posts for the Navigation Menu Lite widget: check Elementor editor pages, Elementor templates, or search database wp_postmeta for meta_value containing 'navigation-menu-lite' or 'plus-nav-menu-lite'
    Affected if The Navigation Menu Lite widget is present in any published content
  3. Inspect menu_hover_click parameter in database
    Query wp_postmeta for the menu_hover_click setting: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%menu_hover_click%'; Also check wp_optimizer (if applicable) for saved widget data
    Affected if The parameter contains unsanitized HTML/script tags (e.g., <script>, javascript:, onerror=) instead of expected values like 'hover' or 'click'
  4. Verify stored XSS execution context
    If menu_hover_click contains suspicious values, inspect the rendered HTML source on the frontend to confirm if the browser interprets the injected content as executable script
    Affected if Injected JavaScript code executes when the affected page loads for other users

User is affected if Plus Addons for Elementor version is 6.4.11 or earlier AND the Navigation Menu Lite widget with a malicious menu_hover_click value is saved in the database.

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 plugin to a version beyond 6.4.11 which contains proper input sanitization and output escaping for the affected parameter.

Recommended fix Moderate confidence

Update to version 6.4.12 or later (check WordPress plugin repository for latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'The Plus Addons for Elementor'
  4. Check the current version - if it is 6.4.11 or below, update to the latest version
  5. Verify the update completes successfully
  6. Test the Navigation Menu Lite widget to ensure functionality remains intact
Caveat Minor plugin update - review changelog for any compatibility notes with Elementor versions

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