CVE-2025-1279 HIGH

CVE-2025-1279: BM Content Builder <= 3.16.2.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Options Update

Vendor Seatheme
Product BM Content Builder
Weakness CWE-862 · Missing authorization
Published April 25, 2025
Last update April 8, 2026

CVSS base score

8.8/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

The BM Content Builder plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the ux_cb_tools_import_item_ajax AJAX action 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 update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

Explanation of Vulnerability in Simple Terms

02Summary

BM Content Builder versions 3.16.2.1 and earlier lack proper authorization checks, allowing authenticated users with low privileges to read, modify, or delete sensitive data and functionality. An attacker with a basic user account can perform actions restricted to administrators without additional interaction. This affects all data and operations within the builder component.

What an attacker can do

03Attacker Capabilities

Read, modify, or delete any data and functionality in the builder with a low-privilege user account.

Potential impact on your site

04Site Impact

Any registered user can access and alter content, settings, and data meant only for administrators.

Conditions required to exploit

05Prerequisites

Attacker must have a valid low-privilege user account on the site; no special interaction required.

Key dates

06Disclosure timeline

April 25, 2025 CVE published
April 8, 2026 Record updated