dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2025-5338

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-26
Fix available
A fix is available. Upgrade to 1.7.1025 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple widgets in all versions up to, and including, 1.7.1028 due to insufficient input sanitization and output escaping on user supplied attributes. 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 plugin for WordPress is vulnerable to Stored Cross-Site Scripting due to insufficient input sanitization and output escaping on user-supplied attributes across multiple widgets. Authenticated attackers with contributor-level access can inject arbitrary JavaScript that executes whenever users access the affected pages.

MitigationUpdate the Royal Elementor Addons plugin to version 1.7.1029 or later where the vulnerability has been patched. Until then, review user access permissions and audit existing pages for injected malicious scripts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Royal Elementor AddonsWordPress extension
Affected:< 1.7.1025

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 Elementor Addons plugin is installed
    Navigate to WordPress Admin > Plugins or run: wp plugin list --name='royal-elementor-addons'
    Affected if Plugin is not installed or not found (not affected by this CVE)
  2. Check installed plugin version
    Look at the plugin version number on the Plugins page in WordPress admin, or run: wp plugin get royal-elementor-addons --field=version
    Affected if Version is less than 1.7.1025 (vulnerable to this CVE)
  3. Identify users with contributor-level access
    Go to WordPress Admin > Users to review user accounts, or run: wp user list --role=contributor --field=user_login,roles
    Affected if At least one contributor account exists and the plugin version is below 1.7.1025 (attack surface is present)
  4. Audit pages built with Royal Elementor widgets
    Inspect pages created using the plugin by viewing page source or using a browser dev tool to examine widget output for script tags, event handlers, or suspicious inline JavaScript
    Affected if Arbitrary script tags or JavaScript event handlers are present in widget-rendered content (potential compromise)
  5. Review recent page revisions for injected code
    Check WordPress page revisions or edit history for any recent changes to pages containing Royal Elementor widgets, looking for unexpected attribute modifications
    Affected if Revisions contain script injections or modified widget attributes not authored by an administrator

You are affected if Royal Elementor Addons version is below 1.7.1025 and you have users with contributor-level or higher access who can edit content with the plugin's widgets.

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
Upgrade available Upgrade to 1.7.1025 or later
Fixed in 1.7.1025
Interim mitigation

Update the Royal Elementor Addons plugin to version 1.7.1029 or later where the vulnerability has been patched. Until then, review user access permissions and audit existing pages for injected malicious scripts.

Recommended fix High confidence

Royal Elementor Addons version 1.7.1025 or later (verify latest version on wordpress.org)

  1. 1. Back up your WordPress site database and files before making any changes.
  2. 2. Log in to your WordPress admin dashboard.
  3. 3. Navigate to Plugins > Installed Plugins.
  4. 4. Locate 'Royal Elementor Addons' in the plugin list.
  5. 5. If an update is available, click 'Update Now' to install the latest version.
  6. 6. Alternatively, download the fixed version from wordpress.org and upload it via Plugins > Add New > Upload Plugin.
  7. 7. After updating, clear any caching plugins or server-side caches.
  8. 8. Verify the plugin is running at version 1.7.1025 or higher under Plugins > Installed Plugins.

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

Fix this in Royal Elementor Addons Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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