CVE-2026-2626
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 · uneditedThe 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
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 confidenceThe divi-booster WordPress plugin before 5.0.2 contains a privilege escalation and PHP object injection vulnerability. The plugin's fixing function lacks both authorization checks and CSRF protections, allowing any unauthenticated visitor to modify stored plugin options. Additionally, the use of unserialize() on user-controlled data enables PHP Object Injection when combined with available gadget chains, potentially leading 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify divi-booster plugin installationLocate the divi-booster plugin folder in wp-content/plugins/ and open the main plugin PHP file to read the version from the plugin header commentAffected if Plugin is present but version is below 5.0.2
-
Compare installed version to affected rangeRead the 'Version:' field from the plugin header and compare numerically to 5.0.2; any version lower than 5.0.2 is affectedAffected if Installed version is less than 5.0.2 (for example, 5.0.1, 4.9.x, or earlier)
-
Check for unauthenticated AJAX/action endpointsExamine the plugin's PHP files for AJAX handlers (wp_ajax_ or wp_ajax_nopriv_ hooks) or action parameters that handle plugin options without checking user capabilitiesAffected if The plugin registers endpoints accessible to unauthenticated users that modify stored options
-
Verify if unserialize processes user inputSearch plugin PHP files for unserialize() calls and trace whether any $_GET, $_POST, or $_REQUEST parameters flow into those callsAffected if The plugin uses unserialize() on data derived from user request parameters
You are affected if divi-booster version is below 5.0.2 and the plugin exposes unauthenticated endpoints that use unserialize on user-controlled data.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to divi-booster version 5.0.2 or later, which adds proper authorization, CSRF protections, and replaces the unsafe unserialize() calls with secure alternatives like json_decode.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2626 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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