# CVE-2024-11952: Classic Addons – WPBakery Page Builder <= 3.0 - Authenticated (Contributor+) Limited Local PHP File Inclusion

> Authenticated contributors can include and execute arbitrary PHP files via the style parameter, potentially leading to code execution or data disclosure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qxvv-ww3j-hm75

## What is CVE-2024-11952?

CVE-2024-11952 is a high-severity path traversal vulnerability in webcodingplace Classic Addons – WPBakery Page Builder, published on 4 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Classic Addons – WPBakery Page Builder plugin for WordPress is vulnerable to Limited Local PHP File Inclusion in all versions up to, and including, 3.0 via the 'style' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, and permissions granted by an Administrator, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. The vulnerability is limited to PHP files in a Windows environment.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2024-11952 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11952 is a high-severity path traversal vulnerability in webcodingplace Classic Addons – WPBakery Page Builder, published on 4 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11952 in the wild and no public exploit code.

Affected product: webcodingplace Classic Addons – WPBakery Page 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-11952/ (Markdown: https://insights.sbomify.com/CVE-2024-11952/index.md)
```

## Sources

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

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