CVE-2026-0664
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 · uneditedThe Royal Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'button_text' parameter in all versions up to, and including, 1.7.1049 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 confidenceThe Royal Addons for Elementor plugin for WordPress versions up to 1.7.1049 suffers from a stored XSS vulnerability in the 'button_text' parameter. Authenticated users with contributor-level access or higher can inject malicious JavaScript through this parameter due to insufficient input sanitization and lack of proper output escaping, causing the script to execute whenever users access affected pages.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Royal Addons for Elementor is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Royal Addons for Elementor' in the listAffected if The plugin is installed and active
-
Check the installed version numberOn the Plugins page, locate Royal Addons for Elementor and note the version number displayed under the plugin nameAffected if Version is 1.7.1049 or lower (the vulnerable version range)
-
Identify widgets using the button_text parameterReview Elementor widget library for Royal Addons widgets that include button_text settings (typically button-style widgets such as call-to-action, dual button, or button group widgets)Affected if Any Royal Addons widgets with button_text functionality are available in the page builder
-
Inspect pages for widget usage with custom button textEdit pages/posts in Elementor and check if any Royal Addons button widgets have custom button_text values applied in the widget settings panelAffected if Affected widgets are in use with custom button_text values entered
-
Review user role permissionsGo to Users > All Users in WordPress admin and examine which users have Contributor-level access or higherAffected if One or more users with Contributor, Author, Editor, or Administrator roles exist on the site (these roles can exploit the vulnerability)
A site is affected if Royal Addons for Elementor version 1.7.1049 or lower is installed, any button widgets with custom button_text are in use, and users with contributor-level access or higher exist on the site.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the Royal Addons for Elementor plugin to a version beyond 1.7.1049. If an update is unavailable, implement server-side sanitization (e.g., sanitize_text_field) for the button_text input and apply output escaping (e.g., esc_html or esc_attr) when rendering the value.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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