Powerpack For Beaver BuilderWordPress extension · Ideabox
CVE-2024-37410
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in IdeaBox Creations PowerPack Lite for Beaver Builder powerpack-addon-for-beaver-builder.This issue affects PowerPack Lite for Beaver Builder: from n/a through <= 1.3.0.3.
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 confidenceA Remote File Inclusion (RFI) vulnerability in the PowerPack Lite for Beaver Builder plugin allows attackers to include arbitrary remote files via improperly validated user input in PHP include/require statements. This can lead to remote code execution. The vulnerability exists in versions 1.3.0.3 and below.
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 For Beaver BuilderWordPress extension
< 1.3.0.4CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Check plugin versionLocate the plugin's main file (powerpack-lite-beaver-builder/powerpack.php) or readme.txt and look for the Version header or changelog entry. In WordPress admin, go to Plugins > Installed Plugins and find PowerPack Lite for Beaver Builder to see its version number.Affected if The installed version is 1.3.0.3 or lower, meaning it is before the patched version 1.3.0.4.
-
Verify plugin is activeIn WordPress admin, navigate to Plugins > Installed Plugins and confirm whether PowerPack Lite for Beaver Builder is currently activated.Affected if The plugin is active and the version is in the affected range, exposing the vulnerability.
-
Identify vulnerable code patternsIf file access is available, examine PHP files in the plugin directory for include, include_once, require, or require_once statements that use unsanitized variables (such as $_GET, $_POST, or $_REQUEST) directly in the path. Look for patterns like 'include($_REQUEST["..."]' without validation functions.Affected if The plugin contains include/require statements using user input without proper validation, confirming the vulnerable code is present.
-
Check for module exposureThe RFI vulnerability typically affects frontend-facing functionality. If accessible, review the Beaver Builder page builder settings where PowerPack modules are used, as the vulnerable code likely executes when certain module parameters are submitted.Affected if PowerPack modules that use the vulnerable include/require logic are accessible to users, creating an exploitable attack surface.
You are affected if PowerPack Lite for Beaver Builder is installed at version 1.3.0.3 or below AND the plugin is active, allowing unauthenticated attackers to inject arbitrary remote files via improper validation in include/require statements.
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 · scoped1.3.0.4
Upgrade to a patched version of PowerPack Lite for Beaver Builder that implements proper input validation on all include/require statements to prevent arbitrary file inclusion. If no patch exists, disable the plugin until a fix is available.
PowerPack Lite for Beaver Builder version 1.3.0.4
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find PowerPack Lite for Beaver Builder (or Powerpack For Beaver Builder) in the plugin list
- Check if the current version is below 1.3.0.4
- If vulnerable, click 'Update Now' to update to version 1.3.0.4 or later
- Verify the update completed successfully and the plugin is now at version 1.3.0.4 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Powerpack For Beaver Builder
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37410 — 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-37410 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