dbcve.org
UltraaddonsPlugin / extension · Codeastrology

CVE-2024-4866

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-10
Fix available
A fix is available. Upgrade to 1.1.7 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 UltraAddons – Elementor Addons (Header Footer Builder, Custom Font, Custom CSS,Woo Widget, Menu Builder, Anywhere Elementor Shortcode) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple widgets in all versions up to, and including, 1.1.6 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. CVE-2024-37554 is potentially a duplicate of this.

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 UltraAddons WordPress plugin for Elementor contains a stored XSS vulnerability in multiple widgets up to version 1.1.6. Authenticated attackers with contributor-level access can inject malicious scripts through unsanitized user-supplied attributes that are insufficiently escaped on output.

MitigationUpdate UltraAddons plugin to version 1.1.7 or later where the vulnerability is patched. If no update is available, disable the plugin or restrict contributor-level user capabilities until a fix is released.

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
UltraaddonsPlugin / extension
Affected:< 1.1.7

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. Identify if UltraAddons plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'UltraAddons' or check the /wp-content/plugins/ directory for the ultraaddons folder
    Affected if The UltraAddons plugin is present on the WordPress site
  2. Determine the installed UltraAddons version
    In WordPress admin, go to Plugins > Installed Plugins > UltraAddons and view the version number displayed, or read the main plugin file header in /wp-content/plugins/ultraaddons/ultraaddons.php for the 'Version' tag
    Affected if The version is 1.1.6 or lower (anything below 1.1.7)
  3. Check if contributor-level user accounts exist
    In WordPress admin, go to Users and review user roles. Contributor role can be identified by accessing a user profile and checking the Role dropdown, or query the wp_usermeta table for meta_value 'contributor'
    Affected if At least one user account with Contributor role exists on the site
  4. Verify Elementor page builder is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm Elementor is installed and activated, as UltraAddons is an Elementor addon
    Affected if Elementor is installed and active, enabling the UltraAddons widgets to function
  5. Confirm UltraAddons widgets are in use
    Check published pages/posts by viewing them in the Elementor editor, or query wp_posts for post_content containing 'ultraaddons' shortcode or element metadata
    Affected if Pages or posts contain UltraAddons widgets, meaning user-supplied attributes could be injected with malicious scripts

The site is affected if UltraAddons version 1.1.6 or lower is installed, Elementor is active, and contributor-level users exist with content editing capability.

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

Update UltraAddons plugin to version 1.1.7 or later where the vulnerability is patched. If no update is available, disable the plugin or restrict contributor-level user capabilities until a fix is released.

Recommended fix High confidence

1.1.7

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the UltraAddons – Elementor Addons plugin
  4. Check if the current version is below 1.1.7
  5. If vulnerable, click 'Update Now' to update to version 1.1.7
  6. Alternatively, download version 1.1.7 from the WordPress Plugin Repository and upload manually via Plugins > Add New > Upload Plugin
  7. After update, verify the plugin version shows 1.1.7

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

Fix this in Ultraaddons Scoped from the published advisory
  • Consultation3.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,260
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,016.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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