dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2025-3813

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-31
Fix available
A fix is available. Upgrade to 1.7.1021 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 and Templates plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘_elementor_data’ parameter in all versions up to, and including, 1.7.1020 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 and Templates WordPress plugin is vulnerable to stored XSS via the '_elementor_data' parameter in versions up to 1.7.1020. Insufficient input sanitization allows authenticated users with Contributor-level permissions to inject arbitrary JavaScript that executes when other users access affected pages.

MitigationUpdate the Royal Elementor Addons and Templates plugin to version 1.7.1021 or later to apply the patch. Review and sanitize existing page content that may contain injected 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.1021

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
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Royal Elementor Addons and Templates'. Note the version number displayed below the plugin name.
    Affected if Plugin is installed with version below 1.7.1021
  2. Confirm plugin version is vulnerable
    Compare the installed version number to the affected range: any version less than 1.7.1021 is vulnerable.
    Affected if Installed version is 1.7.1020 or lower
  3. Check for _elementor_data usage in post meta
    Query the wp_postmeta table for posts containing '_elementor_data' in the meta_key field. Use SQL: SELECT post_id, meta_value FROM wp_postmeta WHERE meta_key = '_elementor_data' LIMIT 10; Examine if raw/unsanitized data appears in meta_value.
    Affected if Posts contain unescaped HTML/JavaScript in _elementor_data meta values
  4. Identify Contributor-level users
    In WordPress admin, go to Users > All Users. Check if any users exist with the 'Contributor' role. Alternatively query: SELECT user_id FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%contributor%';
    Affected if At least one Contributor-level user account exists in the WordPress installation

If the Royal Elementor Addons plugin is installed at version 1.7.1020 or lower AND the _elementor_data meta field is in use on any posts AND Contributor-level users exist, the environment is affected by this stored XSS vulnerability.

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.1021 or later
Fixed in 1.7.1021
Interim mitigation

Update the Royal Elementor Addons and Templates plugin to version 1.7.1021 or later to apply the patch. Review and sanitize existing page content that may contain injected scripts.

Recommended fix High confidence

Royal Elementor Addons and Templates version 1.7.1021

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Royal Elementor Addons and Templates' in the plugin list
  4. Click 'Update now' to update the plugin to version 1.7.1021
  5. Verify the update completed successfully by confirming the version number is 1.7.1021

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

Fix this in Royal Elementor Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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