# CVE-2024-12239: PowerPack Lite for Beaver Builder <= 1.3.0.5 - Reflected Cross-Site Scripting via Navigate Parameter

> Unauthenticated attackers can inject scripts via the navigate parameter, potentially compromising administrative users who click malicious links.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Dec 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-r4xg-5xjw-6vvv

## What is CVE-2024-12239?

CVE-2024-12239 is a medium-severity cross-site scripting vulnerability in ideaboxcreations PowerPack Lite for Beaver Builder, published on 17 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-12239?

It affects 1 product.


Products: Ideabox Powerpack for Beaver Builder.

## How do I fix CVE-2024-12239?

No fix has been published for CVE-2024-12239 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-12239 being exploited?

There is no known exploitation of CVE-2024-12239 in the wild and no public exploit code.

## Other vulnerabilities in ideaboxcreations PowerPack Lite for Beaver Builder

- [CVE-2024-43330](https://insights.sbomify.com/CVE-2024-43330/): WordPress PowerPack for Beaver Builder plugin < 2.37.4 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2024-2289](https://insights.sbomify.com/CVE-2024-2289/): PowerPack Lite for Beaver Builder <= 1.3.0 - Authenticated(Contributor+) Stored Cross-Site Scripting via element link (medium 6.4)
- [CVE-2022-0176](https://insights.sbomify.com/CVE-2022-0176/): PowerPack Lite for Beaver Builder < 1.2.9.3 - Reflected Cross-Site Scripting (medium 6.1)
- [CVE-2024-37409](https://insights.sbomify.com/CVE-2024-37409/): WordPress PowerPack Lite for Beaver Builder plugin <= 1.3.0.4 - Cross Site Scripting (XSS) vulnerability (medium 5.9)
- [CVE-2024-37410](https://insights.sbomify.com/CVE-2024-37410/): WordPress PowerPack Lite for Beaver Builder plugin <= 1.3.0.3 - Local File Inclusion vulnerability (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12239 and fix it if it is affected.

What it is: CVE-2024-12239 is a medium-severity cross-site scripting vulnerability in ideaboxcreations PowerPack Lite for Beaver Builder, published on 17 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-12239 in the wild and no public exploit code.

Affected product: ideaboxcreations PowerPack Lite for Beaver Builder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-12239/ (Markdown: https://insights.sbomify.com/CVE-2024-12239/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-12239
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-12239
- OSV: https://osv.dev/vulnerability/CVE-2024-12239

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-12239/
Summaries are generated and may contain mistakes; the official description above is the record.