CVE-2024-5455
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 · uneditedThe Plus Addons for Elementor Page Builder plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 5.5.4 via the 'magazine_style' parameter within the Dynamic Smart Showcase widget. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
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 confidenceThe Plus Addons for Elementor plugin versions up to 5.5.4 contains a Local File Inclusion vulnerability in the Dynamic Smart Showcase widget's 'magazine_style' parameter. Authenticated attackers with Contributor-level access can manipulate this parameter to include arbitrary files from the server, enabling PHP code execution and potentially bypassing access controls.
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< 5.6.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the Plus Addons for Elementor plugin is installedCheck your WordPress plugin directory for 'Plus Addons For Elementor' or 'the-plus-addons-for-elementor' folder, typically in wp-content/plugins/Affected if The plugin folder exists in your WordPress installation
-
Determine the installed plugin versionAccess WordPress admin > Plugins > Plus Addons For Elementor and read the version number displayed, or inspect the plugin's main PHP file header for 'Version:' tagAffected if The version number is less than 5.6.0 (versions 5.5.4 and below are vulnerable)
-
Identify if Dynamic Smart Showcase widget is in useSearch your Elementor pages/posts for the 'Dynamic Smart Showcase' widget by reviewing page content or using a database query on wp_posts where post_content contains 'dynamic-smart-showcase' or the widget's unique identifierAffected if The Dynamic Smart Showcase widget is actively used on your site
-
Check web server access logs for suspicious file inclusion requestsReview access logs (Apache/Nginx) for requests to pages containing the Dynamic Smart Showcase widget with unusual 'magazine_style' parameter values, such as paths like ../../../../etc/passwd or PHP files outside the web rootAffected if Log entries show requests with manipulated magazine_style parameters containing directory traversal patterns (../) or unusual file paths
You are affected if the Plus Addons for Elementor plugin is installed with a version below 5.6.0 AND the Dynamic Smart Showcase widget is in use, allowing an authenticated contributor-level user to potentially exploit the magazine_style parameter for local file inclusion.
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.6.0
Upgrade to version 5.5.5 or later which patches the LFI vulnerability. Until then, restrict contributor-level access and monitor for suspicious file inclusion requests in the Dynamic Smart Showcase widget.
5.6.0
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'The Plus Addons for Elementor' in the plugin list
- Check the current version number to confirm it is below 5.6.0
- Click 'Update Now' if an update is available, or click 'Check for updates' and then update
- Verify the update completed successfully by confirming the version now shows 5.6.0
- Test the Dynamic Smart Showcase widget functionality to ensure the fix does not break legitimate features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5455 — 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-5455 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