Skip to main content
VulnerabilityPublished

CVE-2026-19907: The Shipo plugin for WordPress is vulnerable to Authentication Bypass in versions 1.6 through 1.8.0

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-19907· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical.

Data as of 14 Nov 2026, 16:17 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.19.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
shipoShipoAffected
  • >=1.6 <=1.8.0
Fixed in–

AI-suggested

Until a fix is available, restrict access to the REST API endpoints and monitor for suspicious activity involving the Shipo plugin. Avoid exposing the REST API publicly if possible.

Description

The Shipo WordPress plugin versions 1.6 through 1.8.0 contain an authentication bypass vulnerability. This flaw arises because the plugin's authenticate_rest_user() function improperly trusts the LOGGED_IN_COOKIE value without verifying its cryptographic signature. Attackers can bypass intended route restrictions and impersonate any user, including administrators, via the REST API, enabling unauthorized actions such as creating new administrator accounts.

References

Community reviews

Loading reviews…