shipo · Shipo · CWE-287 · published 2026-11-14

CVE-2026-19907Shipo 1.6 - 1.8.0 - Authentication Bypass to Administrator

Routine No exploitation evidence; EPSS 0.5%.

CVE-2026-19907 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 41% of all CVEs. This Shipo vulnerability: CVSS 9.8 (v3.1), attacks can be automated, a successful attack gives total control of the component. Routine: patch when convenient.

Share this

Remediation#

No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.5% (41th pct)FIRST EPSS v2026.06.15
CVSS base score9.8 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Weakness: CWE-287: Improper Authentication

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →