CVE intelligence and bounded remediation
CVE-2026-2626 — divi-booster security vulnerability
The divi-booster WordPress plugin before 5.0.2 does not have authorization and CSRF checks in one of its fixing function, allowing unauthenticated users to modify stored divi-booster WordPress plugin before 5.0.2 options. Furthermore, due to the use of unserialize() on the data, this could be further exploited when combined with a PHP gadget chain to achieve PHP Object Injection
- Severity
- High
- CVSS
- 8.1 (3.1)
- Published
- 2026-03-11
- CISA KEV
- Not currently listed
- Ecosystem
- php/wordpress
- Weaknesses
- CWE-352, CWE-502
Affected products
No browser-safe affected-product rows are available.
Matched remediation archetype
Unsafe deserialization and object reconstruction
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory serialization formats accepted from requests, queues, caches, files, cookies, and cross-service messages.
- Trace whether untrusted input can select classes, types, callbacks, constructors, or object hooks during decoding.
- Identify signing, schema validation, trust-boundary, and compatibility settings for each decoder.
Remediate safely
- Replace native object deserialization with a data-only format and explicit schema validation.
- If replacement is not immediate, use a safe decoder with a minimal type allowlist and disable polymorphic or executable hooks.
- Update the affected library and add inert tests for unknown types, extra fields, malformed nesting, and unsigned data.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.