# CVE-2026-10749: Post Duplicator < 3.0.15 - Contributor+ PHP Object Injection via customMetaData

> Contributors can inject PHP objects via custom metadata in Post Duplicator, potentially leading to code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-57q8-6wvw-p94h

## What is CVE-2026-10749?

CVE-2026-10749 is a high-severity unsafe deserialization vulnerability in Unknown Post Duplicator, published on 24 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Post Duplicator WordPress plugin before 3.0.15 does not safely handle custom meta-data during post duplication, storing attacker-supplied serialized values without the WordPress meta API's double-serialization protection, allowing users with Contributor-level access and above to inject a PHP Object.

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


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

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

## Is CVE-2026-10749 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10749 is a high-severity unsafe deserialization vulnerability in Unknown Post Duplicator, published on 24 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10749 exists.

Affected product: Unknown Post Duplicator. 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-10749/ (Markdown: https://insights.sbomify.com/CVE-2026-10749/index.md)
```

## Sources

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

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