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

CVE-2026-3311

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
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 plugin's Progress Bar shortcode in all versions up to, and including, 6.4.9 due to insufficient input sanitization and output escaping on user supplied attributes. 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.9 contain a Stored XSS vulnerability in the Progress Bar shortcode. Authenticated attackers with contributor-level access can inject arbitrary JavaScript via unsanitized user-supplied attributes in the shortcode, which executes when other users access the affected pages.

MitigationUpgrade to plugin version 6.5.0 or later which includes proper input sanitization and output escaping for the Progress Bar shortcode attributes.

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 Plus Addons for Elementor is installed
    Navigate to WordPress admin > Plugins and locate 'Plus Addons for Elementor' in the installed plugins list
    Affected if The plugin is not listed in the active plugins
  2. Determine the installed plugin version
    Click on the plugin in the WordPress plugins list to view its version number, or check the plugin header in /wp-content/plugins/the-plus-addons-for-elementor/includes/plus-version.php
    Affected if The installed version is earlier than 6.5.0
  3. Identify pages using the Progress Bar shortcode
    Search the WordPress database or content files for the shortcode [plus_progress_bar] or search posts/pages containing 'progress_bar' in the content, or use a plugin audit to find shortcode usage
    Affected if The Progress Bar shortcode is present in any published content
  4. Inspect Progress Bar shortcode attributes for injection
    Review the actual shortcode content in posts/pages - look for unexpected javascript:, onload=, onerror=, or similar event handlers in the shortcode attributes
    Affected if Shortcode attributes contain unexpected JavaScript event handlers or URI schemes

You are affected if Plus Addons for Elementor version is below 6.5.0 AND the Progress Bar shortcode is in use on your site, allowing any contributor-level user to potentially inject malicious scripts

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 plugin version 6.5.0 or later which includes proper input sanitization and output escaping for the Progress Bar shortcode attributes.

Recommended fix Moderate confidence

6.5.0 or latest version available on wordpress.org

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'The Plus Addons for Elementor' in the plugin list
  4. Check the current version number to confirm it is 6.4.9 or earlier
  5. If an update is available, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/the-plus-addons-for-elementor/ and upload it manually
  7. After updating, verify the new version number in the Plugins list
  8. Test the Progress Bar widget/shortcode functionality to ensure it works correctly

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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