dbcve.org
Premium Addons For ElementorWordPress extension · Leap13

CVE-2025-4774

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 4.11.9 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 Premium Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the data-countdown attribute of Countdown widget in all versions up to, and including, 4.11.8 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

Premium Addons for Elementor plugin versions up to 4.11.8 contain a stored XSS vulnerability in the Countdown widget. The data-countdown attribute lacks proper input sanitization and output escaping, allowing authenticated Contributors or higher to inject malicious JavaScript that executes for all users accessing affected pages.

MitigationUpdate Premium Addons for Elementor to version 4.11.9 or later. Audit existing content using the Countdown widget for any injected malicious 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
Premium Addons For ElementorWordPress extension
Affected:< 4.11.9

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 the installed version of Premium Addons for Elementor
    Navigate to Plugins > Installed Plugins in WordPress admin, locate 'Premium Addons for Elementor' by Leap13, and check the version number displayed. Alternatively, check the plugin's main PHP file header or the readme.txt file for the Version constant.
    Affected if The displayed version is 4.11.8 or lower (any version below 4.11.9).
  2. Identify pages using the Countdown widget
    In Elementor editor, review all pages and posts. Look for the Premium Countdown widget in the widget panel. Check each page/post that uses this widget by editing with Elementor and examining the widget settings panel on the left side.
    Affected if Any published page or post contains the Premium Addons Countdown widget.
  3. Inspect Countdown widget data-countdown attribute
    With Elementor editor open on a page containing the Countdown widget, click the widget to select it. In the left panel under Content tab, examine the 'Countdown' or 'Due Date' field where users enter the target date/time. View the page source or use browser dev tools to inspect the rendered HTML for the data-countdown attribute on the widget container.
    Affected if The data-countdown attribute value contains unsanitized characters such as <script>, javascript:, onerror=, onload=, or other HTML/JavaScript event handlers.
  4. Review recent changes by Contributor-level users
    In WordPress admin, go to Posts > All Posts or Pages > All Pages. Check the revision history or activity log for any recent edits made by users with Contributor role. Examine the content of those revisions for suspicious script tags or event handlers in Countdown widget settings.
    Affected if Any Countdown widget configuration was edited by a Contributor-level user and contains malicious script injection.

You are affected if the Premium Addons for Elementor plugin version is below 4.11.9 AND any published page uses the Countdown widget with a malicious payload in the data-countdown attribute.

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.11.9 or later
Fixed in 4.11.9
Interim mitigation

Update Premium Addons for Elementor to version 4.11.9 or later. Audit existing content using the Countdown widget for any injected malicious scripts.

Recommended fix High confidence

Premium Addons For Elementor version 4.11.9 or later

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find 'Premium Addons For Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 4.11.9 or later
  5. After updating, verify the Countdown widget functions correctly on your pages
  6. Clear any site caching plugins if implemented
  7. Consider using a security plugin to scan for any remaining XSS issues

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-2025-4774 — 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-4774 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