dbcve.org
Beaver BuilderWordPress extension · Fastlinemedia

CVE-2025-4102

HIGH · 7.2 CVSS v3.1 Published 2025-06-20
Fix available
A fix is available. Upgrade to 2.9.1.1 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Beaver Builder Plugin (Starter Version) plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'save_enabled_icons' function in all versions up to, and including, 2.9.1. This makes it possible for authenticated attackers, with Administrator-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. The vulnerability was partially patched in version 2.9.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Beaver Builder Plugin (Starter Version) for WordPress versions up to 2.9.1 lacks file type validation in the save_enabled_icons function, allowing authenticated administrators to upload arbitrary files. This arbitrary file upload vulnerability enables remote code execution on the affected server.

MitigationUpdate to the patched version immediately. Until then, restrict administrator-level access and implement server-side file upload restrictions (e.g., file type allowlists, upload directory isolation, and executable file prevention).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Beaver BuilderWordPress extension
Affected:< 2.9.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Beaver Builder plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Beaver Builder Plugin (Starter Version)' or check the plugins directory for the beaver-builder folder.
    Affected if The Beaver Builder plugin is present in the WordPress installation.
  2. Check installed Beaver Builder version
    In WordPress admin, go to Plugins > Installed Plugins and locate Beaver Builder Plugin. The version number is displayed below the plugin name. Alternatively, check the main plugin file (usually wp-content/plugins/beaver-builder/lite-version.php or similar) for the 'Version' header.
    Affected if The installed version is lower than 2.9.1.1.
  3. Confirm administrator role exists
    In WordPress admin, go to Users > All Users and verify if any user with Administrator role exists. The vulnerability requires administrator-level access to exploit.
    Affected if There is at least one user with Administrator role who can access the Beaver Builder settings.
  4. Check if save_enabled_icons function is accessible
    The vulnerable function save_enabled_icons handles icon settings in Beaver Builder. Inspect network requests when an administrator saves icon settings in Beaver Builder > Settings > Icons to see if the endpoint responds.
    Affected if An authenticated administrator can access the Beaver Builder icon settings save functionality.

The environment is affected if Beaver Builder Plugin (Starter Version) is installed with a version lower than 2.9.1.1 AND an administrator-level user exists who can access the plugin's icon settings save feature.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.9.1.1 or later
Fixed in 2.9.1.1
Interim mitigation

Update to the patched version immediately. Until then, restrict administrator-level access and implement server-side file upload restrictions (e.g., file type allowlists, upload directory isolation, and executable file prevention).

Recommended fix High confidence

2.9.1.1

  1. 1. Create a complete backup of your WordPress site (database and files) before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the Beaver Builder plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to version 2.9.1.1 or later.
  5. 5. Alternatively, download the latest version from the official WordPress plugin repository or from wpbeaverbuilder.com.
  6. 6. After updating, verify the plugin version shows 2.9.1.1 or higher in the Plugins list.
  7. 7. Test that the Beaver Builder functionality works correctly on your site.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Beaver Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4102 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4102 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data