CVE-2025-11160

WPBakery Page Builder <= 8.6.1 - Stored Cross-Site Scripting via Custom JS Module

2025-10-14 17:29
Muhammad Yudha - DJ

Strategic Overview

Status
Patched in 8.7
Affected Plugin
WPBakery Page Builder
Affected Version
<= 8.6.1
CVSS
6.4Medium
Weakness type
CWE-80 · Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
CVE
CVE-2025-11160
View all WPBakery Page Builder vulnerabilities

At a glance

CVE-2025-11160 is a medium-severity Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in the WPBakery Page Builder WordPress plugin, affecting versions <= 8.6.1. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 8.7; sites on affected versions should update now. Disclosed October 2025, reported by Muhammad Yudha - DJ.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

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

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as <, >, and & that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.

Remediation

Update to version 8.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WPBakery Page Builder: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPBakery Page Builder 8.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C