dbcve.org
Unlimited Elements For ElementorWordPress extension · Unlimited Elements

CVE-2024-0367

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-30
Fix available
A fix is available. Upgrade to after 1.5.96 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 Unlimited Elements For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the link field of an installed widget (e.g., 'Button Link') in all versions up to, and including, 1.5.96 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 Unlimited Elements For Elementor plugin for WordPress versions up to 1.5.96 contains a stored XSS vulnerability in the link field functionality of widgets. Authenticated users with contributor-level permissions can inject arbitrary JavaScript via unsanitized user-supplied attributes in the Button Link field, which executes when other users access the affected pages.

MitigationUpgrade the Unlimited Elements For Elementor plugin to version 1.5.97 or later. If immediate upgrade is not possible, restrict contributor-level user permissions until the patch can be applied.

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
Unlimited Elements For ElementorWordPress extension
Affected:<= 1.5.96

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 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Unlimited Elements For Elementor' in the list
    Affected if The plugin is present in the WordPress installation
  2. Check the installed version
    In Plugins list, find Unlimited Elements For Elementor and note the version number displayed below the plugin name
    Affected if The version is 1.5.96 or lower
  3. Identify widgets using link fields
    Open pages built with Elementor in the editor, look for widgets that contain Button Link or similar link field functionality provided by Unlimited Elements
    Affected if Widgets with link fields from this plugin are in use on the site
  4. Inspect link field content for malicious scripts
    In Elementor editor, examine the URL and attributes fields in Button Link settings for any script: or javascript: prefixes, or unusual HTML/JS content
    Affected if Suspicious script injection is present in link field attributes
  5. Review contributor-level user accounts
    Go to Users > All Users in WordPress admin and check for accounts with Contributor role
    Affected if Contributor-level users exist who could exploit this vulnerability

The environment is affected if the plugin version is 1.5.96 or lower AND contributor-level users exist AND link fields from this plugin are being used on the site.

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 a release after 1.5.96
Interim mitigation

Upgrade the Unlimited Elements For Elementor plugin to version 1.5.97 or later. If immediate upgrade is not possible, restrict contributor-level user permissions until the patch can be applied.

Recommended fix Moderate confidence

1.5.97 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'Unlimited Elements For Elementor' in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually upload version 1.5.97 or later from the WordPress plugin repository
  5. 5. After updating, verify the plugin version shows 1.5.97 or higher under Plugins > Installed Plugins
  6. 6. Clear any caching plugins or server-side caches to ensure the fix takes effect

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

Fix this in Unlimited Elements For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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