CVE-2026-5162
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 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.
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 fails to properly sanitize and escape user input in the Instagram Feed widget's 'instagram_follow_text' parameter, allowing authenticated users with Contributor-level access or higher to inject malicious JavaScript that executes when other users view the affected page.
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 installedNavigate to WordPress Admin > Plugins and locate Royal Addons for Elementor in the installed plugins list, or inspect the plugin directory at wp-content/plugins/royal-addons-for-elementor/Affected if The plugin is installed and active on the WordPress site
-
Determine the installed plugin versionIn the WordPress plugins list, click on the plugin to view its details and note the version number, or read the Version header from the main plugin PHP fileAffected if The installed version is lower than 1.7.1057 (the patched release)
-
Identify use of the Instagram Feed widgetSearch the WordPress database or inspect Elementor templates for instances of the Royal Instagram Feed widget. Check pages, posts, or Elementor templates where this specific widget has been addedAffected if The Instagram Feed widget from Royal Addons is present and configured on any published page or template
-
Inspect the instagram_follow_text parameterEdit any page containing the Instagram Feed widget, locate the widget settings panel, and examine the 'Follow Text' or 'instagram_follow_text' field for any custom JavaScript, HTML tags, or suspicious contentAffected if The parameter contains unescaped HTML, script tags, or JavaScript event handlers that were manually entered
A user is affected if Royal Addons for Elementor is installed with a version below 1.7.1057 AND the Instagram Feed widget with a non-empty 'instagram_follow_text' parameter is in use 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 Royal Addons for Elementor to version 1.7.1057 or later, which includes proper input sanitization and output escaping for the affected widget parameter.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5162 — 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-5162 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