CVE-2026-19907
Deferred Deferred - Pending Action

Authentication Bypass in Shipo WordPress Plugin

Vulnerability report for CVE-2026-19907, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-14

Last updated on: 2026-11-14

Assigner: Wordfence

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-14
Last Modified
2026-11-14
Generated
2026-11-15
AI Q&A
2026-11-14
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
shipo Shipo From 1.6 (inc) to 1.8.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-287 When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Shipo WordPress plugin versions 1.6 to 1.8.0 has an authentication bypass flaw. The `authenticate_rest_user()` function allows unauthenticated attackers to impersonate any user, including administrators, by exploiting a missing cryptographic signature check on the `LOGGED_IN_COOKIE`. Attackers can also bypass route restrictions by inserting `/wp-json/shipo/` in unrelated REST API queries.

Detection Guidance

Check WordPress sites using the Shipo plugin versions 1.6 through 1.8.0. Review REST API logs for unauthorized access attempts or suspicious activity involving the /wp-json/shipo/ endpoint or query strings containing that substring. Use commands like grep to search for plugin versions in WordPress installations.

Impact Analysis

Unauthenticated attackers can gain full control of your WordPress site by creating admin accounts, modifying content, or stealing sensitive data. Since the flaw allows impersonation of any user, it poses a severe risk to site integrity and confidentiality.

Compliance Impact

This vulnerability could lead to unauthorized access and data breaches, violating GDPR's data protection requirements and HIPAA's security rules. Organizations may face fines or legal consequences if user data is compromised due to this flaw.

Mitigation Strategies

Immediately update the Shipo plugin to the latest patched version if available. If no patch exists, disable the Shipo plugin entirely. Review all user accounts for unauthorized changes and revoke any suspicious administrator accounts created via the vulnerability.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-19907. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...