dbcve.org
Exclusive Addons For ElementorWordPress extension · Exclusiveaddons

CVE-2025-4783

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-27
Fix available
A fix is available. Upgrade to 2.7.9.2 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 Exclusive Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the HTML attributes of the Countdown Timer Widget in all versions up to, and including, 2.7.9.1 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

The Exclusive Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting in the Countdown Timer Widget due to insufficient input sanitization and output escaping of HTML attributes. Authenticated attackers with Contributor-level access or higher can inject malicious JavaScript via widget attributes that persists and executes when users access affected pages.

MitigationUpdate the Exclusive Addons for Elementor plugin to version 2.7.9.2 or later. Until patched, review existing pages using the Countdown Timer Widget and remove or restrict contributor-level user permissions.

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
Exclusive Addons For ElementorWordPress extension
Affected:< 2.7.9.2

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 Exclusive Addons for Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Exclusive Addons for Elementor' in the list
    Affected if The plugin is not found in the installed plugins list
  2. Check installed plugin version
    In Plugins list, click on the plugin name or view the plugin details to see the version number displayed
    Affected if The installed version is lower than 2.7.9.2 (for example, 2.7.9, 2.7.8, 2.6.x, etc.)
  3. Identify pages using Countdown Timer Widget
    In Elementor editor, search for pages containing the Countdown Timer widget, or use a plugin/grep to search post content for 'countdown-timer' or 'exclusive-addons-elementor' widget references in the wp_posts database table
    Affected if Any page, post, or custom post type contains an active Countdown Timer widget from this plugin
  4. Review user roles with contributor-level or higher access
    In WordPress admin, go to Users > All Users and review the role column for accounts with Contributor, Author, Editor, or Administrator roles
    Affected if There are multiple users with Contributor-level or higher access, especially those you do not personally manage or trust

You are affected if the Exclusive Addons for Elementor plugin version is below 2.7.9.2 AND any Countdown Timer Widget is actively used on your site with untrusted users having contributor-level access.

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

Update the Exclusive Addons for Elementor plugin to version 2.7.9.2 or later. Until patched, review existing pages using the Countdown Timer Widget and remove or restrict contributor-level user permissions.

Recommended fix High confidence

2.7.9.2

  1. Backup the WordPress site database and files before making any changes
  2. Navigate to Dashboard > Plugins in WordPress admin
  3. Locate 'Exclusive Addons For Elementor' in the plugins list
  4. Click 'Update now' when version 2.7.9.2 is available, or manually upload/download the plugin version 2.7.9.2 from the WordPress repository
  5. Verify the plugin version shows 2.7.9.2 after update
  6. Clear any caching mechanisms if the site uses caching (server-level cache, CDN cache, etc.)

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

Fix this in Exclusive Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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