CVE-2025-26885: Beaver Builder WordPress Assistant · Deserialization of Untrusted Data
Affects Beaver Builder WordPress AssistantSource CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Beaver Builder WordPress Assistant | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, users should monitor Beaver Builder's communications for updates. Applying general best practices such as restricting access to the plugin and limiting input sources may reduce risk but are not specific mitigations for this vulnerability.
Description
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.