dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2024-1500

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 1.3.92 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 Logo Widget in all versions up to, and including, 1.3.91 due to insufficient input sanitization and output escaping on user supplied URLs. This makes it possible for authenticated attackers with contributor-level and above permissions 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 plugin for WordPress contains a stored XSS vulnerability in the Logo Widget. Authenticated users with contributor-level or higher permissions can inject malicious scripts through unsanitized URL inputs. The plugin fails to properly sanitize input and escape output when rendering user-supplied URLs, allowing arbitrary JavaScript execution in users' browsers when they access affected pages.

MitigationUpdate the Royal Elementor Addons and Templates plugin to version 1.3.92 or later. If no update is available, implement custom input sanitization using WordPress functions like esc_url() and output escaping with appropriate functions in the Logo Widget template.

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

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 plugin is installed
    Navigate to WordPress admin dashboard > Plugins and locate Royal Elementor Addons and Templates in the installed plugins list
    Affected if The plugin is present in the plugins directory
  2. Identify installed plugin version
    In the Plugins list, click on the plugin details to view the installed version number, or check the plugin header file for the Version constant
    Affected if Version is lower than 1.3.92 (for example, 1.3.91, 1.3.90, etc.)
  3. Determine if Logo Widget is in use
    Review active pages and templates for instances of the Logo Widget component from Royal Elementor Addons
    Affected if The Logo Widget is actively used on any published page or template
  4. Inspect Logo Widget URL configuration
    Edit any page or template containing the Logo Widget, open the widget settings panel, and examine the URL field in the widget configuration
    Affected if The URL field accepts raw input without visible sanitization or the configured URL contains unsanitized user-supplied content

A user is affected if the Royal Elementor Addons plugin version is below 1.3.92 AND the Logo Widget with a URL configuration is actively in use on the 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
Upgrade available Upgrade to 1.3.92 or later
Fixed in 1.3.92
Interim mitigation

Update the Royal Elementor Addons and Templates plugin to version 1.3.92 or later. If no update is available, implement custom input sanitization using WordPress functions like esc_url() and output escaping with appropriate functions in the Logo Widget template.

Recommended fix High confidence

1.3.92 or later

  1. 1. Backup your WordPress site (database and files)
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find 'Royal Elementor Addons and Templates' in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. Alternatively, manually download version 1.3.92 or later from wordpress.org/plugins/royal-elementor-addons/
  6. 6. Deactivate and delete the current plugin version, then upload and install the updated version
  7. 7. After update, clear any caching plugins and verify the logo widget functions correctly

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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