dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2025-39361

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to 1.7.1018 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WP Royal Royal Elementor Addons royal-elementor-addons allows Stored XSS.This issue affects Royal Elementor Addons: from n/a through <= 1.7.1017.

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 · moderate confidence

Stored XSS vulnerability in Royal Elementor Addons plugin allows injection of malicious JavaScript through unsanitized user input that gets rendered in web pages without proper encoding, affecting all versions up to 1.7.1017.

MitigationUpdate Royal Elementor Addons to the latest version (greater than 1.7.1017) when available. Review the site for any compromise and ensure admin accounts are secure.

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.1018

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. Confirm Royal Elementor Addons is installed
    Check the WordPress plugins dashboard or inspect the plugin files in wp-content/plugins/royal-elementor-addons to verify the plugin is present on the site
    Affected if Plugin is installed and active on the WordPress site
  2. Identify the installed version
    Locate the main plugin file (usually royal-elementor-addons.php) and check the version header, or view the plugin version in the WordPress plugins admin panel
    Affected if Version is less than 1.7.1018 (any version up to and including 1.7.1017)
  3. Review pages using the plugin for suspicious content
    Inspect page source or database for unexpected script tags, event handlers, or iframe insertions in content areas where Royal Elementor Addons widgets are used
    Affected if Malicious JavaScript code is present in post content, page builder templates, or widget settings
  4. Check for unauthorized admin accounts
    Navigate to Users > All Users in WordPress admin and review the list for unknown administrator accounts or recent account creations
    Affected if Unexpected admin accounts exist or account creation dates coincide with the vulnerability window

A user is affected if Royal Elementor Addons plugin is installed with version 1.7.1017 or lower, since the stored XSS vulnerability exists in this version range.

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.1018 or later
Fixed in 1.7.1018
Interim mitigation

Update Royal Elementor Addons to the latest version (greater than 1.7.1017) when available. Review the site for any compromise and ensure admin accounts are secure.

Recommended fix High confidence

1.7.1018

  1. Backup your WordPress site before making any changes
  2. Update Royal Elementor Addons to version 1.7.1018 or later via WordPress admin dashboard (Plugins > Royal Elementor Addons > Update Now)
  3. Alternatively, upload the updated plugin manually via Plugins > Add New > Upload Plugin
  4. After updating, clear any caching plugins or server-side caches
  5. Verify the update was successful by checking the plugin version in 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
  • 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-39361 — 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-39361 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