CVE-2026-19907Shipo Improper Authentication
Wordfence
Vulnerability Summary
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.
CVSS v3.1 Base Metrics — Score 9.8 (CRITICAL)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
Affected & Patched Versions
- Shipo 1.6 - 1.8.0
- Shipo 1
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is critical.
- Check whether you run Shipo and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 14, 2026Published
- Nov 14, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Shipo CVEsYou are reading CVE-2026-19907. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsMore Shipo CVEs
External References
Data last checked: Nov 14, 2026 03:00 UTC