Shipo 1.6 - 1.8.0 - Authentication Bypass to Administrator
Strategic Overview
- Status
- Patched in 1.8.1
- Affected Plugin
- Shipo
- Affected Version
1.6 – 1.8.0- CVSS
- 9.8Critical
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-19907
At a glance
CVE-2026-19907 is a critical-severity Improper Authentication vulnerability in the Shipo WordPress plugin, affecting versions 1.6 – 1.8.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.8.1; sites on affected versions should update now. Disclosed November 2026, reported by Nabil Irawan.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-287: Improper Authentication
Shipo 1.6 – 1.8.0 carries this weakness at authenticate_rest_user(), and reaching it takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For Shipo the fix is 1.8.1: builds 1.6 – 1.8.0 are affected, anything from 1.8.1 onward is not.
Remediation
Update to version 1.8.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Shipo 1.8.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C