dbcve.org
Powerpack Addons For ElementorWordPress extension · Powerpackelements

CVE-2024-24843

HIGH · 8.8 CVSS v3.1 Published 2024-02-21
Fix available
A fix is available. Upgrade to after 2.10.8 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in PowerPack Addons for Elementor PowerPack Pro for Elementor.This issue affects PowerPack Pro for Elementor: from n/a before 2.10.8.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in PowerPack Pro for Elementor plugin allows attackers to potentially trick authenticated administrators into performing unintended actions (such as modifying plugin settings or content) due to missing or improper CSRF token validation in the plugin's admin functionality.

MitigationUpdate PowerPack Pro for Elementor to version 2.10.8 or later which contains the CSRF protection fix. Until patched, limit admin sessions and avoid clicking untrusted links while logged into the WordPress admin panel.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check the installed version of PowerPack Addons For Elementor
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PowerPack Addons For Elementor' or 'PowerPack Pro for Elementor' to view the version number. Alternatively, inspect the main plugin file (usually powerpack/includes/class-powerpack.php or similar) and look for the 'Version' header comment.
    Affected if The displayed version is 2.10.8 or lower (e.g., 2.10.7, 2.10.6, etc.)
  2. Verify the plugin is active
    In WordPress admin, confirm the PowerPack plugin shows as 'Active' in the Plugins list.
    Affected if The plugin is installed and active in the WordPress environment
  3. Confirm admin access to PowerPack settings exists
    Navigate to the WordPress admin panel and check if you can access PowerPack menu items (typically under 'PowerPack' in the left sidebar or within Elementor settings). Try opening the plugin's settings pages.
    Affected if You can access PowerPack admin settings pages without being blocked or redirected

A user is affected if PowerPack Addons for Elementor version 2.10.8 or lower is installed and active with accessible admin settings in their WordPress environment.

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 2.10.8
Interim mitigation

Update PowerPack Pro for Elementor to version 2.10.8 or later which contains the CSRF protection fix. Until patched, limit admin sessions and avoid clicking untrusted links while logged into the WordPress admin panel.

Recommended fix Moderate confidence

2.10.9 or later

  1. 1. Log in to the WordPress admin dashboard where the PowerPack Addons for Elementor plugin is installed.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate 'PowerPack Addons for Elementor' (or 'PowerPack Pro for Elementor' if using the Pro version).
  4. 4. If an update is available, click 'Update Now' to update to the latest version which contains the security fix.
  5. 5. Alternatively, download the latest version from the official WordPress repository or from the developer's website and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is running on version 2.10.9 or later by checking the plugin version number.

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

Fix this in Powerpack 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-24843 — 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-24843 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