Authenticated object injection via Create Post API deserialization
Published Mar 3, 2025 · Updated Apr 29, 2026
Deserialization in Beaver Builder Assistant 1.5.1 and earlier allows remote authenticated users to inject PHP objects through the Create Post API. The Create Post API deserializes attacker-controlled request data, but public sources do not identify the parameter or PHP function. Editor-level access is required, and secondary code or SQL injection, path traversal, or service interruption additionally requires a suitable POP chain.
Summary
What happened
Deserialization in Beaver Builder Assistant 1.5.1 and earlier allows remote authenticated users to inject PHP objects through the Create Post API. The Create Post API deserializes attacker-controlled request data, but public sources do not identify the parameter or PHP function. Editor-level access is required, and secondary code or SQL injection, path traversal, or service interruption additionally requires a suitable POP chain.
The record
- CVE
- CVE-2025-26885
- Published
- Mar 3, 2025
- Updated
- Apr 29, 2026
- Vendor
- Beaver Builder
- Product
- Assistant
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 3, 2025CVE publishedPublication date reported by the CVE source.
- Apr 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.5.1 changes=[{"at":"1.5.1.1","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo