dbcve.org
Exclusive Addons For ElementorWordPress extension · Exclusiveaddons

CVE-2024-2503

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to 2.6.9.3 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 Post Grid Widget in all versions up to, and including, 2.6.9.2 due to insufficient input sanitization and output escaping on user supplied tags. 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. CVE-2024-32557 is likely a duplicate of this issue.

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 (XSS) in the Post Grid Widget. The vulnerability exists due to insufficient input sanitization and output escaping on user-supplied tags, allowing authenticated attackers with contributor-level access or higher to inject arbitrary JavaScript that executes when users access affected pages.

MitigationUpdate the Exclusive Addons for Elementor plugin to version 2.6.9.3 or later. Until the update is applied, review pages using the Post Grid Widget and remove any untrusted content.

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

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 present on the site
  2. Check the installed version
    In the plugins list, note the version number displayed under the plugin name. Compare this version to the affected range: versions prior to 2.6.9.3 are vulnerable
    Affected if the installed version is lower than 2.6.9.3
  3. Identify pages using the Post Grid Widget
    Review pages and posts edited with Elementor. Open each in the Elementor editor and check if a Post Grid Widget has been added to the layout
    Affected if the Post Grid Widget is present on any published page
  4. Inspect Post Grid Widget tag settings
    With Elementor, click on the Post Grid Widget and examine the Tags settings under the widget options. Look for any custom tag configurations that accept user input
    Affected if custom tags have been configured in the Post Grid Widget settings
  5. Check for suspicious scripts in affected pages
    View the source of pages containing the Post Grid Widget. Search for unexpected script tags, event handlers (onload, onerror, onclick), or javascript: URIs that may indicate injected XSS payloads
    Affected if arbitrary script tags or event handlers are present in the page source

A user is affected if the Exclusive Addons for Elementor plugin is installed with a version lower than 2.6.9.3 AND the Post Grid Widget is used on the site with custom tag configurations.

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.6.9.3 or later
Fixed in 2.6.9.3
Interim mitigation

Update the Exclusive Addons for Elementor plugin to version 2.6.9.3 or later. Until the update is applied, review pages using the Post Grid Widget and remove any untrusted content.

Recommended fix High confidence

2.6.9.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Exclusive Addons For Elementor' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 2.6.9.3 or later
  5. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is 2.6.9.3 or higher in Plugins > Installed Plugins

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
  • 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-2503 — 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-2503 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