dbcve.org
Premium Addons For ElementorWordPress extension · Leap13

CVE-2024-3885

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to 4.10.29 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 subcontainer value parameter in all versions up to, and including, 4.10.28 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access or 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 Premium Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript via the subcontainer value parameter due to insufficient input sanitization and output escaping in versions up to 4.10.28.

MitigationUpdate the Premium Addons for Elementor plugin to version 4.10.29 or later which includes proper input sanitization and output escaping for the affected parameter.

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

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 Premium Addons for Elementor is installed
    Check your WordPress plugins dashboard or use 'wp plugin list' via WP-CLI to confirm the Premium Addons for Elementor plugin is active on the site
    Affected if The plugin is not present on the system
  2. Check the installed plugin version
    View the plugin details in the WordPress admin under Plugins > Installed Plugins, or inspect the plugin header in the main plugin file to determine the exact version number
    Affected if The installed version is 4.10.28 or earlier (less than 4.10.29)
  3. Identify use of the subcontainer widget
    Search your WordPress content (posts, pages, templates) for instances where the Premium Addons subcontainer widget has been used. This can be done by querying the wp_posts table for Elementor save files or reviewing published content where the widget appears
    Affected if The subcontainer widget has been added to any page, post, or template
  4. Inspect stored subcontainer values for malicious input
    Query the WordPress database (wp_postmeta or wp_posts tables) for any saved subcontainer configurations. Examine the 'subcontainer value' parameter for unsanitized HTML, JavaScript tags, or event handlers (onclick, onerror, etc.)
    Affected if The stored subcontainer value contains unescaped HTML or JavaScript code

You are affected if Premium Addons for Elementor version 4.10.28 or earlier is installed AND the subcontainer widget has been used with user-controlled values containing malicious scripts.

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.10.29 or later
Fixed in 4.10.29
Interim mitigation

Update the Premium Addons for Elementor plugin to version 4.10.29 or later which includes proper input sanitization and output escaping for the affected parameter.

Recommended fix High confidence

Premium Addons For Elementor version 4.10.29

  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' when an update is available, or manually upload version 4.10.29
  5. Verify the plugin version shows 4.10.29 or higher after updating
  6. Clear any caching plugins or server-side caches if applicable

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

Fix this in Premium Addons For Elementor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,010
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,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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