Powerpack For Beaver BuilderWordPress extension · Ideabox
CVE-2024-2289
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 PowerPack Lite for Beaver Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the link in multiple elements in all versions up to, and including, 1.3.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 PowerPack Lite for Beaver Builder WordPress plugin versions up to 1.3.0 suffer from a stored XSS vulnerability. Authenticated users with contributor-level or higher permissions can inject malicious JavaScript through the link attribute in certain elements due to insufficient input sanitization and output escaping. The injected scripts execute whenever users access 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.1CVSS 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.
-
Verify plugin is installedCheck if Ideabox PowerPack For Beaver Builder plugin is active on the WordPress site. This can be done via WordPress admin under Plugins > Installed Plugins, or by checking the /wp-content/plugins/ directory for the plugin folder.Affected if The plugin is installed and active
-
Check installed versionLocate the plugin version number in the WordPress admin (Plugins > Installed Plugins > View Details) or read the main plugin PHP file header which contains the Version field.Affected if Version is less than 1.3.0.1 (any version up to and including 1.3.0)
-
Identify use of affected elementsReview pages, posts, or Beaver Builder layouts that use PowerPack elements with link/URL attributes. Check for any custom links, button elements, or module configurations that accept a link parameter.Affected if Any PowerPack elements with link attributes are in use on the site
-
Audit user role permissionsNavigate to WordPress Users section and review which users have Contributor-level or higher roles. These roles have edit_posts capability required to trigger the vulnerability.Affected if Any users with Contributor, Author, Editor, or Administrator roles exist on the site
The site is affected if the plugin is installed with version 1.3.0 or earlier AND any PowerPack elements with link attributes are being used by users with contributor-level or higher access.
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.1
Update the plugin to a version newer than 1.3.0 which should contain proper sanitization and output escaping. If no update is available, restrict contributor-level users from using the affected elements or temporarily disable the plugin.
1.3.0.1
- Log in to the WordPress admin dashboard
- Navigate to the Plugins section
- Locate 'PowerPack Lite for Beaver Builder' in the installed plugins list
- Click on 'Update now' if an update is available, or manually update to version 1.3.0.1 or later
- Verify the plugin is updated to version 1.3.0.1 or newer after completion
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
- 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-2289 — 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-2289 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