Shipo 1.6 - 1.8.0 - Authentication Bypass to Administrator
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| shipo | Shipo | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Shipo | Shipo |
|
||||||||
| Wordpress-extensions | Shipo |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.467% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Shipo
Shipo shipo Wordpress-extensions Wordpress-extensions shipo |
|
| Vendors & Products |
Shipo
Shipo shipo Wordpress-extensions Wordpress-extensions shipo |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Shipo 1.6 - 1.8.0 - Authentication Bypass to Administrator | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV3_1
|