Powerpack Addons For ElementorWordPress extension · Ideabox

CVE-2024-3668

HIGH · 8.8 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 2.10.18 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 PowerPack Pro for Elementor plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 2.10.17. This is due to the plugin not restricting low privileged users from setting a default role for a registration form. This makes it possible for authenticated attackers, with contributor-level access and above, to create a registration form with administrator set as the default role and then register as an administrator.

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 PowerPack Pro for Elementor plugin fails to enforce proper authorization checks when configuring registration form default roles. Authenticated users with contributor-level permissions can create or modify registration forms to set the default role to administrator, then register a new account that inherits administrator privileges.

MitigationUpdate the plugin to version 2.10.18 or later, which should include capability checks restricting role selection to only those roles the current user is permitted to assign.

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
Powerpack Addons For ElementorWordPress extension
Affected:< 2.10.18

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Confirm plugin installation
    Navigate to WordPress admin > Plugins and locate 'Ideabox Powerpack Addons for Elementor' or 'PowerPack Pro for Elementor' in the installed plugins list
    Affected if Plugin is not installed means not affected
  2. Check installed version
    In WordPress admin > Plugins, view the version number of the PowerPack plugin. Compare to 2.10.18 - versions below this are affected
    Affected if Version is below 2.10.18 indicates vulnerability is present
  3. Identify registration form configurations
    Navigate to Elementor > PowerPack > Registration Forms (or similar path) to list any created registration forms. Look for forms that have a default role setting configured
    Affected if Active registration forms exist with default role assignment options means the vulnerable feature is in use
  4. Verify contributor user role access
    Log in as a user with contributor-level permissions and attempt to access or create a registration form in Elementor. Check if the role selection dropdown is visible and editable by this user level
    Affected if Contributor-level users can modify default role settings indicates the authorization flaw is exploitable
  5. Review current role assignments
    Inspect existing registration form settings for the assigned default role. Check if any forms are configured to assign 'Administrator' as the default role to new users
    Affected if Registration forms set to administrator role and are editable by low-privilege users confirms the vulnerability is exposed

A user is affected if they have the PowerPack plugin installed below version 2.10.18 and have registration forms enabled where contributor-level users can configure or access the default role setting.

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.10.18 or later
Fixed in 2.10.18
Interim mitigation

Update the plugin to version 2.10.18 or later, which should include capability checks restricting role selection to only those roles the current user is permitted to assign.

Recommended fix High confidence

PowerPack Addons For Elementor version 2.10.18

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate 'PowerPack Addons For Elementor' (or 'PowerPack Pro for Elementor') in the plugin list.
  4. 4. If an update is available, click 'Update Now' to update to version 2.10.18 or later.
  5. 5. Alternatively, navigate to Dashboard > Updates and apply available updates for the PowerPack plugin.
  6. 6. After updating, verify the plugin version is 2.10.18 or higher by checking the plugin details.

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

Fix this in Powerpack Addons For Elementor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3668 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-3668 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