dbcve.org
Powerpack For Beaver BuilderWordPress extension · Ideabox

CVE-2024-12239

MEDIUM · 6.1 CVSS v3.1 Published 2024-12-17
Fix available
A fix is available. Upgrade to 1.3.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The PowerPack Lite for Beaver Builder plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the navigate parameter in all versions up to, and including, 1.3.0.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick an administrative user into performing an action such as clicking on a link.

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 confidence

PowerPack Lite for Beaver Builder WordPress plugin versions up to 1.3.0.5 are vulnerable to reflected XSS via the navigate parameter due to insufficient input sanitization and output escaping. Unauthenticated attackers can craft malicious URLs that execute arbitrary JavaScript in an administrator's browser when they click the link.

MitigationUpdate the plugin to a version beyond 1.3.0.5 when available, or implement proper input sanitization and output escaping for the navigate parameter. Additionally, educate administrative users about not clicking untrusted links.

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
Affected:< 1.3.1

CVSS 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm PowerPack Lite plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ideabox Powerpack For Beaver Builder' or 'PowerPack Lite for Beaver Builder'. Note the installed version shown.
    Affected if The plugin is installed and active in the WordPress environment
  2. Verify the installed version number
    Check the plugin version in the plugins list or in the plugin's main PHP file header (typically in /wp-content/plugins/powerpack-lite-for-beaver-builder/ or similar path). Compare the version against the affected range: versions prior to 1.3.1 (vulnerable: 1.3.0.5 and below)
    Affected if Installed version is 1.3.0.5 or lower, or any version below 1.3.1
  3. Identify if the navigate parameter is accessible
    Check if the plugin's frontend functionality is accessible by attempting to access a page on the site and examining if the plugin handles URL parameters. Look for any frontend rendering of plugin modules that might process the 'navigate' GET or POST parameter.
    Affected if The plugin is active and its modules that handle navigation parameters are enabled on the site, allowing the 'navigate' parameter to be processed
  4. Check for web application protection
    Inspect any WAF, security plugin, or input filtering in place that may sanitize or block malicious URL parameters. Review server logs for any attempts to inject the 'navigate' parameter with script tags.
    Affected if No WAF, security plugin, or input sanitization is actively filtering the 'navigate' parameter, leaving it exposed to XSS injection

A user is affected if the PowerPack Lite for Beaver Builder plugin is installed with version 1.3.0.5 or lower, the plugin's navigation-handling modules are active, and no protective filtering is blocking malicious 'navigate' parameter values.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.3.1 or later
Fixed in 1.3.1
Interim mitigation

Update the plugin to a version beyond 1.3.0.5 when available, or implement proper input sanitization and output escaping for the navigate parameter. Additionally, educate administrative users about not clicking untrusted links.

Recommended fix High confidence

1.3.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'PowerPack Lite for Beaver Builder' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 1.3.1 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  5. Verify the updated version number reflects 1.3.1 after the update completes
  6. Clear any caching mechanisms if the site uses caching plugins

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12239 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12239 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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