CVE-2025-12558

Beaver Builder – WordPress Page Builder <= 2.9.4 - Authenticated (Contributor+) Sensitive Information Exposure

2025-12-08 00:00
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-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-12558
View all Beaver Builder Page Builder – Drag and Drop Website Builder vulnerabilities

At a glance

CVE-2025-12558 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor 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 Sensitive Information Exposure in all versions up to, and including, 2.9.4 via the 'get_attachment_sizes' function. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive data including the path and meta data of private attachments, which can be used to view the attachments.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Beaver Builder Page Builder <= 2.9.4 carries this weakness at get_attachment_sizes, and reaching it takes an account at Contributor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. 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?

The fix is the thing that ends this: Beaver Builder Page Builder 2.9.4.1 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12558https://www.wordfence.com/threat-intel/vulnerabilities/id/eb2f6c67-ef4a-4afc-bd61-6c0185e354a8https://nvd.nist.gov/vuln/detail/CVE-2025-12558

Related records

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