# CVE-2026-14602: Remote API <= 0.2 - Unauthenticated PHP Object Injection via remote-api Query Parameter

> Unauthenticated attackers can inject PHP objects via the remote-api parameter, potentially leading to remote code execution if gadget chains exist.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-2jcm-jwvc-6vhm

## What is CVE-2026-14602?

CVE-2026-14602 is a critical unsafe deserialization vulnerability in Unknown Remote API, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Remote API WordPress plugin through 0.2 does not authenticate a request before deserializing user-supplied input, allowing unauthenticated attackers to inject arbitrary PHP objects, which can lead to remote code execution when a suitable gadget chain is present through another installed Remote API WordPress plugin through 0.2.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-14602 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14602 is a critical unsafe deserialization vulnerability in Unknown Remote API, published on 30 Jul 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-14602 exists.

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

## Sources

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

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