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

CVE-2026-6504

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 Royal Elementor Addons and Templates plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title_tag' parameter in all versions up to, and including, 1.7.1058 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 Royal Elementor Addons WordPress plugin fails to properly sanitize the 'title_tag' parameter and escape output, allowing authenticated users with Contributor-level permissions to inject persistent malicious JavaScript that executes when other users view affected pages.

MitigationUpdate the Royal Elementor Addons plugin to a version newer than 1.7.1058, or apply input sanitization using WordPress sanitization functions and output escaping via esc_attr() or similar functions on the title_tag 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. Confirm Royal Elementor Addons is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate Royal Elementor Addons in the list
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    In the Plugins list, locate the version number displayed beneath the plugin name Royal Elementor Addons
    Affected if The version number is 1.7.1058 or lower
  3. Verify if Contributor-level users exist
    Go to WordPress admin > Users and check if any users have the Contributor role assigned
    Affected if There are users with Contributor-level permissions who have access to create or edit content using the plugin
  4. Inspect pages using the title_tag feature
    Review pages built with Royal Elementor Addons that contain elements utilizing the title_tag parameter (such as header or title widgets)
    Affected if Pages are published or previewable by users other than the contributor who created them
  5. Check for suspicious script injections in page content
    Use WordPress admin to view page source or use a database query to search the wp_posts table for script tags or javascript: URLs in content fields
    Affected if Unexpected script tags or event handlers are found in title_tag-related fields

A user is affected if Royal Elementor Addons version 1.7.1058 or lower is installed, the plugin is active, and users with Contributor permissions can create or edit content using the plugin's title_tag feature.

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 Royal Elementor Addons plugin to a version newer than 1.7.1058, or apply input sanitization using WordPress sanitization functions and output escaping via esc_attr() or similar functions on the title_tag parameter.

Recommended fix Moderate confidence

Royal Elementor Addons and Templates version 1.7.1059 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Royal Elementor Addons and Templates' in the plugin list
  4. Check if an update is available (version higher than 1.7.1058)
  5. If update available, click 'Update Now' to install the fixed version
  6. After update, verify the plugin is running version 1.7.1059 or higher

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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