Powerpack For Beaver BuilderWordPress extension · Ideabox
CVE-2024-37409
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 Neutralization of Input During Web Page Generation ('Cross-site Scripting') 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.4.
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 stored Cross-site Scripting (XSS) vulnerability exists in PowerPack Lite for Beaver Builder plugin versions 1.3.0.4 and below. The plugin fails to properly sanitize user input during web page generation, allowing authenticated attackers to inject malicious JavaScript scripts that execute in the context of other users' browsers when they view affected pages.
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.5CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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.
-
Confirm PowerPack Lite for Beaver Builder is installedAccess your WordPress admin panel and navigate to Plugins > Installed Plugins. Locate 'Ideabox PowerPack Lite for Beaver Builder' or 'PowerPack Lite' in the list to verify the plugin is present and active.Affected if The plugin is installed and active in WordPress.
-
Identify the installed plugin versionIn the WordPress plugin list, click on the plugin to view its details, or check the plugin's main PHP file header for the 'Version' comment. Alternatively, look for a changelog file within the plugin directory that may list version history.Affected if The version displayed is 1.3.0.4 or below, indicating the installation is within the vulnerable range.
-
Verify the specific affected componentReview the plugin settings and any Beaver Builder layouts or pages where PowerPack modules have been used. The vulnerability exists in web page generation, so check any custom content modules, button modules, or custom code modules provided by PowerPack that accept user input.Affected if Any PowerPack module that accepts and displays user-generated content is enabled and used on pages.
-
Determine if authentication is required for exploitationNote that this is an authenticated stored XSS. Assess whether contributor-level or higher user accounts exist in your WordPress environment that could potentially inject malicious scripts through plugin input fields.Affected if User accounts with contributor, author, editor, or administrator roles exist in the WordPress site.
Your environment is affected if PowerPack Lite for Beaver Builder is installed with version 1.3.0.4 or below and any modules accepting user input are actively used on your site.
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.5
Upgrade PowerPack Lite for Beaver Builder to the latest version that includes proper input sanitization and output encoding. If a patch is unavailable, disable the plugin until a fix is released.
PowerPack Lite for Beaver Builder version 1.3.0.5
- Update PowerPack Lite for Beaver Builder plugin to version 1.3.0.5 or later
- Verify the update was applied successfully through the WordPress plugin admin panel
- Test the affected functionality to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Powerpack For Beaver Builder
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37409 — 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-37409 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