BM Content Builder <= 3.16.2.1 - Missing Authorization to Authenticated (Subscriber+) Stored Cross-Site Scripting via ux_cb_page_options_save
Strategic Overview
- Status
- Patched in 3.16.3
- Affected Plugin
- BM Content Builder
- Affected Version
<= 3.16.2.1- CVSS
- 6.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-1777
At a glance
CVE-2025-1777 is a medium-severity Missing Authorization vulnerability in the BM Content Builder WordPress plugin, affecting versions <= 3.16.2.1. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.16.3; sites on affected versions should update now. Disclosed June 2025, reported by István Márton.
Vulnerability Overview
The BM Content Builder plugin for WordPress is vulnerable to unauthorized modification of data to a missing capability check on the 'ux_cb_page_options_save' function in all versions up to, and including, 3.16.2.1. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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-862: Missing Authorization
BM Content Builder <= 3.16.2.1 carries this weakness at ux_cb_page_options_save, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For BM Content Builder the fix is 3.16.3: builds <= 3.16.2.1 are affected, anything from 3.16.3 onward is not.
Remediation
Update to version 3.16.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: BM Content Builder 3.16.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in BM Content Builder
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C