Shipo 1.6–1.8.0: A Cookie That Was Never Checked (CVE-2026-19907, CVSS 9.8)

Running Shipo on your site? Check it against CVE-2026-19907 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Shipo is in the affected range (1.6 – 1.8.0), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Shipo 1.6–1.8.0: A Cookie That Was Never Checked (CVE-2026-19907, CVSS 9.8)

The plugin read the username out of the logged-in cookie and believed it — no signature check, no verification of any kind. Anyone who knows an administrator's username could be signed in as that administrator. That is CVE-2026-19907 in the Shipo WooCommerce courier plugin, scoring CVSS 9.8, disclosed November 14, 2026 (CNA: Wordfence).

What Happened

CVE-2026-19907 is an unauthenticated authentication bypass vulnerability (CWE-287, Improper Authentication) in the Shipo plugin (wordpress.org slug shipo, 30 active installs on the directory listing at disclosure time).

Am I Affected?

Check wp-admin → Plugins for Shipo and its version. Between 1.6 and 1.8.0 inclusive, your store runs the affected code. Knowing a username is not a meaningful barrier — WordPress usernames are routinely public through author archives and REST user listings.

Our scanner checks it: run the free mini-scan, or check just this plugin at /tools/plugin-check?slug=shipo. The check reads the version your site announces and flags anything in the 1.6–1.8.0 range. A version above 1.8.0 earns no strength and no clean bill from this check, because the CVE record names no patched version — silence is the honest answer there. The check never sends a crafted cookie or a REST request — it reads the public version disclosure only.

What To Do Now

  1. Update Shipo to the newest available release today, and confirm in the vendor changelog that the authentication handling changed.
  2. Audit administrator accounts. Look for administrator users you do not recognize, especially any created through the REST API.
  3. Review recently created accounts of any role and remove anything you cannot explain — a created admin is the record's own named endgame for this flaw.

The Bigger Lesson

A cookie's contents are a claim, not a proof. The username inside a session cookie means nothing until the cookie's cryptographic signature verifies — authentication material that is parsed but not verified is just attacker-supplied text with extra steps. Any code that reads identity out of a client-supplied value must verify that value first, every time.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the account audit finds something you do not recognize.


Running a WooCommerce store with Shipo? Update to the newest release today, audit your administrator accounts, then run the free check at preshipit.com/free-scan — our scanner checks it, version-checking this plugin against CVE-2026-19907 from the version your site announces to the world.

Check Shipo on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls Shipo's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-19907 included. No scan, no account.

Open the free plugin checker →

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Running Shipo on your site? Check it against CVE-2026-19907 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Shipo is in the affected range (1.6 – 1.8.0), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report