Shipo
Shipo 1.6 - 1.8.0 - Authentication Bypass to Administrator
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1.6, <= 1.8.0
Mitigation
The record names no fix. Check the vendor advisory below.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.3 not a PoC · 1 suspicious or fake
Not a PoC 3
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Xuchen-Li/cv-arxiv-daily | 7 Feb 2024 −2.8 y | 48 | Not a PoC · unrelated |
| XuzhaoLi/ro-arxiv-daily | 11 Feb 2024 −2.8 y | 36 | Not a PoC · unrelated |
| Noorts/duckdb-changelog | 2 Oct 2025 −1.1 y | 0 | Not a PoC · unrelated |
Suspicious or fake 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| GHLists/new-cves | 24 Sep 2026 −51 d | 0 | Suspicious · score 60
Why suspicious
|
Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. Do not run PoC code from unknown sources.