dbcve.org
Premium Addons For ElementorWordPress extension · Leap13

CVE-2024-2664

MEDIUM · 6.4 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 4.10.25 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Premium Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Countdown Widget in all versions up to, and including, 4.10.24 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 Premium Addons for Elementor plugin before version 4.10.25 contains a stored XSS vulnerability in its Countdown Widget. Authenticated attackers with contributor-level permissions can inject malicious JavaScript through insufficiently sanitized user-supplied attributes, which then executes when other users access the compromised pages.

MitigationUpdate Premium Addons for Elementor to version 4.10.25 or later. Audit existing pages using the Countdown Widget for any injected payloads, and consider resetting sessions for high-privilege users as a precaution.

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
Premium Addons For ElementorWordPress extension
Affected:< 4.10.25

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Premium Addons for Elementor is installed
    Navigate to Plugins > Installed Plugins in WordPress admin and locate Premium Addons for Elementor in the list
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    Click on the plugin name or view details to see the installed version number
    Affected if The installed version is below 4.10.25 (for example, 4.10.24 or earlier)
  3. Identify pages using the Countdown Widget
    In Elementor editor, search for pages containing the Countdown widget, or check the WordPress database for posts with 'premium-countdown' in the postmeta table
    Affected if Any pages are using the Countdown Widget from this plugin
  4. Inspect Countdown Widget settings for injected scripts
    Edit each page with the Countdown Widget and examine all text fields (especially labels, button text, and timer display options) for suspicious JavaScript tags or event handlers
    Affected if Any unexpected script tags, javascript: URIs, or onload/onerror attributes are found in widget settings

You are affected if Premium Addons for Elementor is installed, the version is below 4.10.25, and any page uses the Countdown Widget which may contain injected malicious scripts.

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 4.10.25 or later
Fixed in 4.10.25
Interim mitigation

Update Premium Addons for Elementor to version 4.10.25 or later. Audit existing pages using the Countdown Widget for any injected payloads, and consider resetting sessions for high-privilege users as a precaution.

Recommended fix High confidence

Premium Addons For Elementor version 4.10.25

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Premium Addons for Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or click 'Check for updates' first if needed
  5. Confirm the update to version 4.10.25 or higher
  6. Verify the update was successful by checking the plugin version

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

Fix this in Premium Addons For Elementor 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-2024-2664 — 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-2664 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