CVE-2026-19907: Shipo (WordPress plugin) · Improper Authentication
Affects Shipo (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 14 Nov 2026, 12:47 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 9.8 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| shipoShipo | Affected
| Fixed in– |
AI-suggested
Since the vulnerability affects self-hosted WordPress plugins, users should immediately disable or remove the Shipo plugin versions 1.6 through 1.8.0 to prevent exploitation. Monitor the vendor's official channels for updates or patches. Avoid exposing the REST API endpoints unnecessarily until a fix is released.
Description
The Shipo WordPress plugin versions 1.6 through 1.8.0 contain an authentication bypass vulnerability. The flaw arises because the authenticate_rest_user() function accepts a LOGGED_IN_COOKIE value and authenticates the user without verifying the cookie's cryptographic signature. Additionally, the intended restriction to the /wp-json/shipo/ REST API route can be bypassed by including that substring in the query string of other REST endpoints. This allows unauthenticated attackers who know a valid username to impersonate that user, including administrators, and perform privileged actions such as creating new administrator accounts.