# CVE-2026-116389: WordPress Phoenix Media Rename plugin <= 3.13.5 - PHP Object Injection vulnerability


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-9r7q-mmwg-3fhm

## What is CVE-2026-116389?

CVE-2026-116389 is a high-severity vulnerability in crossi72 Phoenix Media Rename, published on 28 Oct 2026. 

### Official description

Deserialization of Untrusted Data vulnerability in crossi72 Phoenix Media Rename phoenix-media-rename allows Object Injection.This issue affects Phoenix Media Rename: from n/a through 3.13.5.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-116389 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116389 is a high-severity vulnerability in crossi72 Phoenix Media Rename, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116389 in the wild and no public exploit code.

Affected product: crossi72 Phoenix Media Rename. 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-116389/ (Markdown: https://insights.sbomify.com/CVE-2026-116389/index.md)
```

## Sources

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

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