CVE-2025-12782

Beaver Builder – WordPress Page Builder <= 2.9.4 - Missing Authorization to Authenticated (Contributor+) Builder Status Tampering

2025-12-03 18:08
Athiwat Tiprasaharn (Jitlada)

Strategic Overview

Status
Patched in 2.9.4.1
Affected Plugin
Beaver Builder Page Builder – Drag and Drop Website Builder
Affected Version
<= 2.9.4
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-12782
View all Beaver Builder Page Builder – Drag and Drop Website Builder vulnerabilities

At a glance

CVE-2025-12782 is a medium-severity Missing Authorization vulnerability in the Beaver Builder Page Builder WordPress plugin, affecting versions <= 2.9.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.9.4.1; sites on affected versions should update now. Disclosed December 2025, reported by Athiwat Tiprasaharn (Jitlada).

Vulnerability Overview

The Beaver Builder – WordPress Page Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.9.4. This is due to the plugin not properly verifying a user's authorization in the disable() function. This makes it possible for authenticated attackers, with contributor level access and above, to disable the Beaver Builder layout on arbitrary posts and pages, causing content integrity issues and layout disruption on those pages.

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

Beaver Builder Page Builder <= 2.9.4 carries this weakness at disable(), and reaching it takes an account at Contributor 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 Beaver Builder Page Builder the fix is 2.9.4.1: builds <= 2.9.4 are affected, anything from 2.9.4.1 onward is not.

Remediation

Update to version 2.9.4.1, 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: Beaver Builder Page Builder 2.9.4.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12782https://www.wordfence.com/threat-intel/vulnerabilities/id/710ed734-ca98-4ab3-82d5-359e683ee062https://nvd.nist.gov/vuln/detail/CVE-2025-12782

Related records

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