# CVE-2025-11160: WPBakery Page Builder <= 8.6.1 - Stored Cross-Site Scripting via Custom JS Module

> Authenticated attackers can inject arbitrary scripts via the Custom JS module, leading to code execution or account takeover when users view affected pages.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **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:** 15 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-vqvf-fjc6-jhfg

## What is CVE-2025-11160?

CVE-2025-11160 is a medium-severity cross-site scripting vulnerability in WPBakery Page Builder, published on 15 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WPBakery Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Custom JS module in all versions up to, and including, 8.6.1. This is due to insufficient input sanitization and output escaping of user-supplied JavaScript code in the Custom JS module. This makes it possible for authenticated attackers with contributor-level access or higher to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via the WPBakery Page Builder Custom JS module granted they have access to the WPBakery editor for post types.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2025-11160?

It affects 1 product.


Products: Wpbakery Page Builder.

## How do I fix CVE-2025-11160?

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

## Is CVE-2025-11160 being exploited?

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

## Other vulnerabilities in WPBakery Page Builder

- [CVE-2024-5709](https://insights.sbomify.com/CVE-2024-5709/): WPBakery <= 7.7 - Authenticated (Author+) Local File Inclusion (high 8.8)
- [CVE-2024-43953](https://insights.sbomify.com/CVE-2024-43953/): WordPress Classic Addons – WPBakery Page Builder plugin <= 3.5 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2023-31213](https://insights.sbomify.com/CVE-2023-31213/): WordPress WPBakery Page Builder Plugin < 6.13.0 is vulnerable to Cross Site Scripting (XSS) (medium 6.5)
- [CVE-2025-10006](https://insights.sbomify.com/CVE-2025-10006/): WPBakery Page Builder <= 8.6 - Authenticated (Contributor+) Stored Cross-Site Scripting (medium 6.4)
- [CVE-2025-11161](https://insights.sbomify.com/CVE-2025-11161/): WPBakery Page Builder <= 8.6.1 - Stored Cross-Site Scripting via vc_custom_heading Shortcode (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11160 and fix it if it is affected.

What it is: CVE-2025-11160 is a medium-severity cross-site scripting vulnerability in WPBakery Page Builder, published on 15 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11160 in the wild and no public exploit code.

Affected product: 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-2025-11160/ (Markdown: https://insights.sbomify.com/CVE-2025-11160/index.md)
```

## Sources

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

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