# CVE-2026-111628: 10up Distributor before 2.3.2 PHP Object Injection via set_meta()

> Contributor-level users can achieve arbitrary code execution via PHP object injection in the Distributor WordPress plugin.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-p88q-h74f-qxvq, GHSA-wm53-9j85-ph6h

## What is CVE-2026-111628?

CVE-2026-111628 is a low-severity unsafe deserialization vulnerability in 10up Distributor, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

10up Distributor before 2.3.2 contains a PHP object injection vulnerability that allows Contributor-level users to instantiate PHP objects by double unserializing distributed post meta. Attackers can store a serialized PHP string as meta, which set_meta() in includes/utils.php unserializes on the destination site, storing attacker-defined objects whose impact depends on loaded gadget classes.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-111628 being exploited?

There is no known exploitation of CVE-2026-111628 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111628 is a low-severity unsafe deserialization vulnerability in 10up Distributor, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111628 in the wild and no public exploit code.

Affected product: 10up Distributor. 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-111628/ (Markdown: https://insights.sbomify.com/CVE-2026-111628/index.md)
```

## Sources

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

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