# CVE-2026-2626: Divi Booster < 5.0.2 - Unauthenticated PHP Object Injection

> Unauthenticated attackers can modify plugin options and potentially execute code via PHP object injection due to unsafe deserialization.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-j3fj-mfxv-75x2

## What is CVE-2026-2626?

CVE-2026-2626 is a high-severity unsafe deserialization vulnerability in Unknown divi-booster, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-2626?


## How do I fix CVE-2026-2626?

No fix has been published for CVE-2026-2626 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2626 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2626 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2626 and fix it if it is affected.

What it is: CVE-2026-2626 is a high-severity unsafe deserialization vulnerability in Unknown divi-booster, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2626 exists.

Affected product: Unknown divi-booster. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2626/ (Markdown: https://insights.sbomify.com/CVE-2026-2626/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2626
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2626
- OSV: https://osv.dev/vulnerability/CVE-2026-2626

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2626/
Summaries are generated and may contain mistakes; the official description above is the record.