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

CVE-2026-5159

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-05
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 Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Instagram Feed widget's 'instagram_follow_text' setting in all versions up to, and including, 1.7.1056 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. Note that exploitation requires that an administrator has previously configured the Instagram Feed widget with a valid Instagram access token on the site.

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 Addons for Elementor plugin for WordPress is vulnerable to stored XSS via the Instagram Feed widget's 'instagram_follow_text' setting. The parameter lacks proper input sanitization and output escaping, allowing authenticated Contributor-level users to inject arbitrary JavaScript that executes whenever users access pages containing the widget.

MitigationUpdate Royal Addons for Elementor to version 1.7.1057 or later. Until patched, remove or restrict the Instagram Feed widget configuration from Contributor-level users.

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 Royal Addons for Elementor is installed
    Go to WordPress Dashboard > Plugins and look for 'Royal Addons for Elementor' in the installed plugins list
    Affected if Plugin is not installed - not affected
  2. Check installed plugin version
    In Plugins list, click on the plugin to view version details, or inspect the plugin header in wp-content/plugins/royal-addons-for-elementor/readme.txt
    Affected if Version is earlier than 1.7.1057 - potentially affected
  3. Identify pages using Instagram Feed widget
    Search post content for 'instagram-feed' shortcode or check Elementor pages for the Royal Instagram Feed widget
    Affected if No Instagram Feed widgets in use - not affected
  4. Inspect Instagram Feed widget settings for suspicious content
    Edit any page containing the Instagram Feed widget, click the widget, and examine the 'Follow Text' field in the widget settings for unsanitized script tags or javascript: links
    Affected if The 'instagram_follow_text' field contains unescaped HTML, script tags, or javascript: handlers - currently exploited
  5. Check for unauthorized Contributor-level accounts
    Go to WordPress Users panel and review user roles; check if any Contributor accounts were created recently or have unusual usernames
    Affected if Untrusted Contributor-level users exist with access to edit content - vulnerable to exploitation

You are affected if Royal Addons for Elementor version is below 1.7.1057 AND the Instagram Feed widget with user-controlled 'follow text' is present on your site.

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 Addons for Elementor to version 1.7.1057 or later. Until patched, remove or restrict the Instagram Feed widget configuration from Contributor-level users.

Recommended fix Moderate confidence

Version higher than 1.7.1056 (latest version available on WordPress.org)

  1. Log in to WordPress admin panel
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Royal Addons for Elementor' in the plugin list
  4. Check if the current version is 1.7.1056 or below
  5. If vulnerable, click 'Update Now' to install the latest version, or manually download the updated plugin from WordPress.org and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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