CVE-2025-1280
Received Received - Intake

Directory Traversal in BM Content Builder WordPress Plugin

Publication date: 2026-09-22

Last updated on: 2026-09-22

Assigner: Wordfence

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-22
Last Modified
2026-09-22
Generated
2026-09-22
AI Q&A
2026-09-22
EPSS Evaluated
N/A
NVD
CVE-2025-1280
EUVD
EUVD-2025-210985

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
bm_content_builder plugin to 3.17.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The BM Content Builder plugin for WordPress has a Directory Traversal vulnerability in versions up to 3.17.1. This flaw exists in the ux_cb_page_customize_save_layout_ajax() function and allows authenticated attackers with Subscriber-level access or higher to read arbitrary files on the server, potentially exposing sensitive data.

Detection Guidance

To detect this vulnerability, check if the BM Content Builder plugin version is below 3.17.1. Use commands like 'wp plugin list' in WordPress or inspect plugin files for the vulnerable function ux_cb_page_customize_save_layout_ajax().

Look for unusual file access patterns or unauthorized file reads in server logs, especially for sensitive files like wp-config.php.

Impact Analysis

If you use the affected BM Content Builder plugin, an attacker could exploit this to access sensitive files on your server, such as configuration files, logs, or other confidential data. This could lead to data breaches or further compromise of your WordPress site.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, which may violate compliance requirements under GDPR, HIPAA, or other regulations. Organizations could face legal penalties, fines, or reputational damage if such a breach occurs due to inadequate security measures.

Mitigation Strategies

Immediately update the BM Content Builder plugin to version 3.17.1 or later. If updating is not possible, remove the plugin until a patch is available.

Review server logs for signs of exploitation and restrict Subscriber-level access to only trusted users.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-1280. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart