On this page (7 sections)

A critical flaw has been published in the Shipo plugin for WordPress. According to the GitHub Advisory Database, versions 1.6 through 1.8.0 accept the value of the logged-in cookie without verifying its cryptographic signature, so an unauthenticated attacker who knows an existing username can act as that user through the WordPress REST API. That includes administrators.

If you run WordPress with Shipo installed, treat this as urgent. The advisory lists no patched version, so you will need to verify the plugin's current state yourself and plan for the case where no fix is available.

What happened

The vulnerability was published on November 14, 2026 through the National Vulnerability Database and in the GitHub Advisory Database. The advisory's references include a WordPress plugin repository changeset and a Wordfence entry. The sources we reviewed do not say who reported the flaw. The NVD record repeats the same text, so it is not independent confirmation.

Only this one advisory chain covers the issue so far. We have not seen a vendor statement, a confirmed fixed version or any report of attacks in the wild, and we do not claim any here.

How the weakness works

The advisory describes an improper authentication problem (CWE-287). Shipo's authenticate_rest_user() function parses the value of the logged-in cookie and authenticates the user named in it, without verifying the cookie's cryptographic signature. In plain terms, the plugin accepts a claim of identity without proof that the claim is genuine.

There is a second problem. The function is meant to apply only to routes under /wp-json/shipo/, but the advisory says that restriction can be bypassed by placing that substring in the query string of an unrelated REST endpoint. That means the weakness is not limited to Shipo's own routes.

The result, according to the advisory, is that an unauthenticated attacker who knows an existing username can impersonate that user and perform authorized actions through the REST API, including creating another administrator account. A newly created administrator would be a separate account, so it could remain after the plugin is removed unless you find and delete it.

Who is realistically exposed

  • Any site with Shipo 1.6 through 1.8.0 installed. The advisory does not say whether an inactive install is reachable, so do not assume it is safe.
  • Sites with administrator accounts whose usernames an outsider could learn or guess. The advisory says the attacker must know an existing username.
  • Sites that cannot restrict REST API access at the web server or firewall level.

The CVSS vector lists network attack, low complexity, no privileges required and no user interaction, which is why the score is 9.8.

How to check your exposure

First find out whether Shipo is installed and which version. This WP-CLI command lists installed plugins with their status and version, so look for a row named shipo and compare the version with 1.6 to 1.8.0. Run it from the WordPress root.

List installed plugins with status and version (run from the WordPress root)WP-CLI
wp plugin list --fields=name,status,version

Next, review your administrator accounts. This command lists all users with the administrator role and their registration dates. Any account you do not recognize, especially one created recently, deserves immediate attention.

List administrator accounts with registration dates (run from the WordPress root)WP-CLI
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered

Then search web server logs for the request pattern the advisory describes: the string shipo appearing in a REST request that is not under the Shipo route. This read-only grep prints matching lines from an Apache-style access log. Adjust the path for your server, and expect legitimate Shipo traffic to appear too, so focus on requests to other REST endpoints.

Search an access log for REST requests mentioning shipoShell
grep -i 'wp-json' /var/log/apache2/access.log | grep -i 'shipo'
Absence of log hits is not proof of safety. Logs may be rotated or incomplete, so rely on the account and file review as well.

What to do now

  1. Confirm whether Shipo is installed and which version is running, using the WP-CLI command above or the Plugins screen.
  2. Check the plugin's page and changelog in the WordPress plugin directory for a version newer than 1.8.0. The advisory lists no patched version, and we have not confirmed that the referenced changeset is the fix, so verify before relying on it.
  3. If a newer release exists, take a backup, update to it, then re-check the version.
  4. If no fixed release is available, deactivate and remove the plugin until the author publishes one, or replace it with an alternative.
  5. Review all administrator accounts and remove any you did not create. Also check editors and other privileged roles.
  6. If you find an unknown admin or suspect misuse, reset passwords for privileged users and invalidate their sessions.
  7. Restrict unauthenticated REST API access with a web server or firewall rule if your site does not need it.
  8. Keep a recent offline backup so you can restore a clean state if the site was altered.
Caution. Deactivating a plugin can break shipping or checkout features that depend on it. If you run a store, test on a staging copy or schedule the change for a quiet period, and have a backup ready first.

Detection and monitoring afterwards

Watch for new administrator accounts, changes to plugin and theme files, and unexpected REST API calls from unfamiliar IP addresses. Alert on any new user with the administrator role. A web application firewall can help limit abuse of REST endpoints, though it is a layer rather than a substitute for removing the vulnerable code; see What is a WAF?.

If you manage many sites, the known vulnerabilities per WordPress plugin page and our guide on whether your WordPress plugin is vulnerable help you track which installs are affected. If you suspect a compromise, follow Website hacked: what to do.

What we do not know yet

  • Which version, if any, fixes the issue. The advisory lists patched versions as unknown.
  • Who reported the flaw, and whether the vendor has acknowledged it publicly.
  • Whether the flaw is being exploited. None of the sources reviewed say so.
  • Whether the plugin must be active to be reachable. The advisory does not specify.

We will update this article if the sources change. Until a fix is confirmed, removing or disabling the plugin is the safest course for a site that can live without it.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-19907 - GitHub Advisory Databasegithub.com
  2. CVE-2026-19907: The Shipo plugin for WordPress is vulnerable to Authentication Bypass in versions 1.6 through 1.8.0.nvd.nist.gov ·
  • WordPress
  • CVE-2026-19907
  • Shipo
  • Authentication bypass
  • REST API