BM Content Builder < 3.17.1 - Authenticated (Subscriber+) Arbitrary File Read
Strategic Overview
- Status
- Patched in 3.17.1
- Affected Plugin
- BM Content Builder
- Affected Version
< 3.17.1- CVSS
- 6.5Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2025-1280
At a glance
CVE-2025-1280 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the BM Content Builder WordPress plugin, affecting versions < 3.17.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.17.1; sites on affected versions should update now. Disclosed September 2026, reported by Tonn.
Vulnerability Overview
The BM Content Builder plugin for WordPress is vulnerable to Directory Traversal in all versions up to 3.17.1 (exclusive) via the ux_cb_page_customize_save_layout_ajax() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.
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. A successful exploit has high impact on confidentiality.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
BM Content Builder < 3.17.1 carries this weakness at ux_cb_page_customize_save_layout_ajax(), and reaching it takes an account at Subscriber level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For BM Content Builder the fix is 3.17.1: builds < 3.17.1 are affected, anything from 3.17.1 onward is not.
Remediation
Update to version 3.17.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: BM Content Builder 3.17.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in BM Content Builder
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C