# CVE-2026-19907 — Shipo

> As of 2026-11-14, CVE-2026-19907 is a CRITICAL-severity vulnerability in Shipo, CVSS v3.1 9.8, EPSS 0.4% (41.0th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-19907 as of 2026-11-14; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-14

## What is CVE-2026-19907?

The Shipo plugin for WordPress is vulnerable to Authentication Bypass in versions 1.6 through 1.8.0. This is due to the `authenticate_rest_user()` function parsing the `LOGGED_IN_COOKIE` value and authenticating the named user without verifying the cookie's cryptographic signature. The function's intended `/wp-json/shipo/` route restriction can also be bypassed by placing that substring in the query string of an unrelated REST endpoint. This makes it possible for unauthenticated attackers who know an existing username to impersonate that user, including an administrator, and perform authorized actions through the REST API, including creating another administrator account.

The record classifies CVE-2026-19907 under weakness class [CWE-287](https://intel.threadlinqs.com/cwe/CWE-287). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 5 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 9.8 — CRITICAL (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **EPSS (FIRST):** 0.4% probability of exploitation in the next 30 days, higher than 41.0% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 6.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-14

## Is CVE-2026-19907 being exploited?

It currently carries a trending score of 40 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **shipo**: Shipo

## How to fix CVE-2026-19907

No vendor patch reference has been recorded for CVE-2026-19907 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-19907

No threat campaign in the Threadlinqs corpus currently references CVE-2026-19907, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

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

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-19907
No Threadlinqs detection currently covers CVE-2026-19907; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
