# Shipo 1.6 - 1.8.0 - Authentication Bypass to Administrator

CVE record · `CVE-2026-19907`

- **Identifiers:** `CVE-2026-19907`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **CNA:** Wordfence
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Technologies:** [Shipo](https://agentprime.io/advisories/technology/shipo.md)
- **Published:** 14 Nov 2026
- **Updated:** 16 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Wordfence) at 14 Nov 2026, 12:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected products, as the CNA wrote them

- Vendor: shipo. Product: Shipo.
  - affected: `1.6 to 1.8.0, inclusive` (semver)
  - Other versions: unaffected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Shipo plugin for WordPress, versions 1.6 through 1.8.0, does not verify the cryptographic signature of the login cookie used for REST API authentication. An unauthenticated attacker who knows an existing username can impersonate that user, including an administrator, and create new administrator accounts. No fixed version is listed.

Written 21 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (Wordfence)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0047, the 41st percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 14 Nov 2026, 12:33 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-19907)
- 14 Nov 2026, 12:39 UTC: First seen by agentprime
- 14 Nov 2026, 13:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-19907)

## Sources

- [CVE List: CVE-2026-19907](https://www.cve.org/CVERecord?id=CVE-2026-19907)
- [NVD: CVE-2026-19907](https://nvd.nist.gov/vuln/detail/CVE-2026-19907)

### References from the CNA

- <https://www.wordfence.com/threat-intel/vulnerabilities/id/ce5ea515-5ae1-4771-9bfb-5a0f4b3fce22?source=cve>
- <https://plugins.trac.wordpress.org/changeset/3701532/shipo>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-19907>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-19907/>. Everything for agents: <https://agentprime.io/llms.txt>.
