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

CVE-2026-40720

HIGH · 7.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Unauthenticated Cross Site Scripting (XSS) in Royal Elementor Addons Pro < 1.7.1041 versions.

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 · moderate confidence

Unauthenticated Cross Site Scripting (XSS) vulnerability in Royal Elementor Addons Pro plugin for WordPress. The flaw allows attackers to inject malicious scripts into web pages without authentication, potentially compromising other users who view the affected content.

MitigationUpdate Royal Elementor Addons Pro to version 1.7.1041 or later. If immediate update is not possible, consider disabling the plugin or implementing Web Application Firewall (WAF) rules to block XSS attack patterns.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 Royal Elementor Addons Pro is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Royal Elementor Addons' or 'Royal Elementor Addons Pro' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'royal-elementor-addons' or similar.
    Affected if The plugin is present on the WordPress site
  2. Identify the installed version number
    In WordPress admin, go to Plugins > Installed Plugins, find Royal Elementor Addons, and note the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file for a 'Version' header in the plugin comment block.
    Affected if A version number is displayed (plugin is active)
  3. Compare version against the fixed release
    Compare your installed version to 1.7.1041. Versions lower than 1.7.1041 are considered affected by this vulnerability.
    Affected if Installed version is lower than 1.7.1041
  4. Review website output for injected scripts
    View pages on your site using browser developer tools (F12) and inspect the page source for any unexpected <script> tags, inline JavaScript events (onclick, onload, onerror), or suspicious external script references that were not added by your team.
    Affected if Unexpected malicious scripts are present in page output
  5. Check for compromise indicators in WordPress
    Review WordPress audit logs, server access logs, or security plugin logs for requests containing XSS payloads (such as <script>, javascript:, or event handlers like onerror=) targeting your site, especially before the plugin was updated.
    Affected if Logs show XSS payload attempts or successful injections

A user is affected if Royal Elementor Addons Pro is installed with a version lower than 1.7.1041, or if malicious scripts have been injected into site content.

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 Royal Elementor Addons Pro to version 1.7.1041 or later. If immediate update is not possible, consider disabling the plugin or implementing Web Application Firewall (WAF) rules to block XSS attack patterns.

Recommended fix High confidence

Royal Elementor Addons Pro 1.7.1041

  1. Backup your WordPress site before making any changes
  2. Update Royal Elementor Addons Pro to version 1.7.1041 or later through the WordPress plugin repository or your site's plugin management interface
  3. Verify the update was successful by checking the installed plugins page
  4. Test critical site functionality to ensure the update did not break any elements

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