dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12934

HIGH · 8.1 CVSS v3.1 Published 2025-12-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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 – WordPress Page Builder plugin for WordPress is vulnerable to unauthorized access and modification of data due to a missing capability check on the 'duplicate_wpml_layout' function in all versions up to, and including, 2.9.4.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary posts with the content of other existing posts, potentially exposing private and password-protected content and deleting any content that is not saved in revisions or backups. Posts must have been created with Beaver Builder to be copied or updated.

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

This is a broken access control vulnerability in the Beaver Builder WordPress plugin. The 'duplicate_wpmlml_layout' function lacks a capability check, allowing any authenticated user with Subscriber-level access or higher to read and overwrite content of arbitrary posts created with Beaver Builder. An attacker can exploit this to expose private/password-protected content and destroy unsaved content by overwriting posts.

MitigationUpdate to version 2.9.5 or later when available. Until then, restrict user registrations or temporarily disable the plugin if possible.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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. Confirm Beaver Builder plugin is installed
    Check the WordPress plugin directory for the Beaver Builder plugin files, typically located at /wp-content/plugins/bb-plugin/ or /wp-content/plugins/beaver-builder-lite-version/
    Affected if Plugin files exist in the plugins directory
  2. Identify the installed Beaver Builder version
    Check the plugin header in the main plugin file (e.g., bb-plugin.php or index.php) for the 'Version' field, or look in WordPress admin under Plugins > Installed Plugins
    Affected if Version is lower than 2.9.5 (the fixed release)
  3. Verify user registration is enabled
    In WordPress admin, go to Settings > General and check 'Anyone can register' is enabled, or inspect the 'users_can_register' option in the wp_options table
    Affected if User registration is enabled and allows Subscriber role or higher
  4. Check for existing user accounts with Subscriber-level access
    In WordPress admin, go to Users > All Users and review the role column, or query wp_users and wp_usermeta tables for users with 'subscriber' role capability
    Affected if Any user account exists with Subscriber, Contributor, Author, or Editor role (these roles all have equal or greater access than Subscriber)
  5. Confirm Beaver Builder post types are in use
    Query the wp_posts table for posts where post_type contains 'fl-builder' or check for Beaver Builder templates/rows in the database
    Affected if Any posts were created using Beaver Builder (the plugin's post types exist in the database)

The environment is affected if Beaver Builder plugin is installed with a version lower than 2.9.5 AND any authenticated user with Subscriber-level or higher access exists on the site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 2.9.5 or later when available. Until then, restrict user registrations or temporarily disable the plugin if possible.

Recommended fix High confidence

Beaver Builder version 2.9.5 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Beaver Builder plugin
  4. Click 'Update now' if an update is available, or manually update to version 2.9.5 or later
  5. Verify the plugin version after update to confirm the fix is applied

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12934 — 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-12934 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