dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-26885

HIGH · 7.2 CVSS v3.1 Published 2025-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Deserialization of Untrusted Data vulnerability in Beaver Builder WordPress Assistant assistant allows Object Injection.This issue affects WordPress Assistant: from n/a through <= 1.5.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 · moderate confidence

This is a PHP Object Injection vulnerability in the Beaver Builder WordPress Assistant plugin caused by deserializing untrusted data. Attackers can potentially achieve remote code execution by injecting malicious PHP objects, especially if other plugins or themes on the same WordPress installation contain exploitable magic methods.

MitigationUpdate the WordPress Assistant plugin to the latest patched version. If no update is available, disable the plugin until a fix is released, as object injection vulnerabilities can lead to remote code execution.

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
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 Assistant plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Beaver Builder Assistant' or check the /wp-content/plugins/ directory for the assistant-plugin folder
    Affected if The plugin is present and active in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, click on the plugin from the Plugins list to view details, or inspect the main plugin PHP file header for 'Version:' value
    Affected if Version number is lower than the patched version released for this vulnerability
  3. Confirm plugin is active
    Check the Plugins > Installed Plugins page to verify the Beaver Builder Assistant plugin status shows as 'Active'
    Affected if The plugin is actively running on the WordPress site
  4. Identify if deserialization of user input occurs
    Review plugin code for use of unserialize() function on data originating from user input (GET, POST, COOKIE, or AJAX requests), or check plugin logs for deserialization activity
    Affected if The plugin deserializes untrusted data from external sources
  5. Audit other plugins for exploitable magic methods
    Review all other installed plugins and the active theme for PHP classes with __wakeup, __destruct, __toString, or __call magic methods that could be chained with the object injection
    Affected if At least one other plugin or theme contains exploitable magic methods that could be triggered via the injected object

The environment is affected if the Beaver Builder Assistant plugin is installed and active with a version vulnerable to CVE-2025-26885 that deserializes untrusted input, especially when combined with exploitable magic methods in other plugins.

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 the WordPress Assistant plugin to the latest patched version. If no update is available, disable the plugin until a fix is released, as object injection vulnerabilities can lead to remote code execution.

Recommended fix Moderate confidence

WordPress Assistant version 1.5.2 or later

  1. Check your current WordPress Assistant plugin version in wp-admin > Plugins
  2. If the installed version is <= 1.5.1, update the plugin to the latest available version
  3. After updating, verify the new version number in wp-admin > Plugins
  4. Test core functionality of the plugin to ensure the update did not break expected behavior
  5. Ensure WordPress core and other plugins are also kept up to date

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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