dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2024-9668

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 1.7.1002 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 plugin's Countdown widget in all versions up to, and including, 1.7.1001 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 and Templates plugin for WordPress is vulnerable to stored Cross-Site Scripting (XSS) in its Countdown widget. Authenticated attackers with contributor-level or higher permissions can inject arbitrary JavaScript through unsanitized user-supplied attributes, which then executes whenever users access the compromised pages.

MitigationUpdate the Royal Elementor Addons and Templates plugin to version 1.7.1002 or later to obtain the security fix that properly sanitizes inputs and escapes outputs in the Countdown widget.

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

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 look for 'Royal Elementor Addons and Templates' in the list
    Affected if The plugin is not installed or has been removed entirely
  2. Check installed plugin version
    In Plugins > Installed Plugins, click on 'View details' for Royal Elementor Addons, or check the plugin header in wp-content/plugins/royal-elementor-addons/readme.txt for the Version field
    Affected if Version number is lower than 1.7.1002 (for example, 1.7.1001, 1.7.100, 1.6.x, etc.)
  3. Identify pages using the Countdown widget
    In WordPress admin, go to All Pages or All Posts and review each for an active Countdown widget. Alternatively, search the wp_postmeta table for meta_value containing 'countdown' or 'wpr-countdown'
    Affected if Any page or post contains a Countdown widget from this plugin
  4. Inspect Countdown widget configuration for injected scripts
    Edit each page with the Countdown widget, open the widget settings, and examine fields like labels, message text, and custom HTML for suspicious <script> tags, javascript: URLs, or onload/onerror event handlers
    Affected if Any Countdown widget settings contain unexpected JavaScript code or HTML attributes like onmouseover, onerror, or onclick

You are affected if the Royal Elementor Addons plugin is installed at a version below 1.7.1002 AND the Countdown widget is being used on your site, as this combination allows stored XSS execution.

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.1002 or later
Fixed in 1.7.1002
Interim mitigation

Update the Royal Elementor Addons and Templates plugin to version 1.7.1002 or later to obtain the security fix that properly sanitizes inputs and escapes outputs in the Countdown widget.

Recommended fix High confidence

Royal Elementor Addons version 1.7.1002

  1. Backup your WordPress site before updating any plugins
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Find 'Royal Elementor Addons and Templates' in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 1.7.1002
  5. Verify the plugin updated successfully to version 1.7.1002 or higher
  6. Clear any caching mechanisms if applicable
  7. Test the Countdown widget to confirm functionality

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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