Element PackWordPress extension · Bdthemes
CVE-2024-24840
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 · uneditedMissing Authorization vulnerability in BdThemes Element Pack Elementor Addons.This issue affects Element Pack Elementor Addons: from n/a through 5.4.11.
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 confidenceA missing authorization vulnerability in BdThemes Element Pack Elementor Addons allows unprivileged users to perform actions they should not have access to. This affects versions up to 5.4.11, potentially enabling unauthorized access to sensitive functionality or data within the Elementor page builder ecosystem.
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
Element PackWordPress extension
< 5.4.12CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Element Pack plugin versionIn WordPress admin, go to Plugins > Installed Plugins. Find 'Element Pack - Elementor Addons' and note the version number displayed beneath the plugin name.Affected if The version shown is any release prior to 5.4.12 (for example: 5.4.11, 5.4.10, 5.3.5, etc.)
-
Verify via plugin file headerAccess the plugin directory via file manager or FTP. Open the main plugin file (typically element-pack.php) and locate the 'Version:' field in the plugin header comment block.Affected if The Version field value is less than 5.4.12
-
Check plugin update statusIn WordPress admin, go to Dashboard > Updates or check the Plugins list for an available update notification for Element Pack.Affected if An update to version 5.4.12 or higher is available, indicating the currently installed version is older
The environment is affected if the installed version of Bdthemes Element Pack is below 5.4.12, as this version range contains the missing authorization vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.4.12
Implement proper capability checks and role-based access controls throughout the plugin, particularly on admin actions and AJAX endpoints. Ensure all user actions verify the current user has appropriate permissions before execution.
Element Pack version 5.4.12
- Back up your WordPress site and database before performing any updates
- Navigate to WordPress admin dashboard > Plugins
- Locate the Element Pack (BdThemes Element Pack Elementor Addons) plugin in the installed plugins list
- Update Element Pack to version 5.4.12 or later
- After updating, verify the plugin version reflects 5.4.12 or higher
- Test the site functionality to ensure the update did not break expected features
- Review user roles and capabilities to ensure proper authorization controls are in place
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Element Pack
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24840 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-24840 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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