CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVE-2026-19907 Shipo 1.6 - 1.8.0 - Authentication Bypass to Administrator
Critical (9.8) in shipo shipo.
On this page
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.
Severity
- CWE
- CWE-287 Improper Authentication
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Modified
- Assigned by
- Wordfence (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-19907 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-19907?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-19907?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-19907 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-19907)
HTML:
<a href="https://cve.bz/cve/CVE-2026-19907"><img src="https://cve.bz/cve/badge/CVE-2026-19907.svg" alt="CVE-2026-19907"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Shipo | from 1.6 through 1.8.0 |
Attack patterns (CAPEC)
- CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
- CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
- CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
- CAPEC-114 Authentication Abuse Severity: Medium
- CAPEC-115 Authentication Bypass Severity: Medium
- CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
- CAPEC-194 Fake the Source of Data Severity: Medium
- CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
- CAPEC-633 Token Impersonation Severity: Medium
- CAPEC-650 Upload a Web Shell to a Web Server Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.