Skip to content
CVE-2026-19907: Update Shipo after an administrator authentication bypass

CVE-2026-19907: Update Shipo after an administrator authentication bypass

November 14, 2026

If your WordPress store uses Shipo 1.6 through 1.8.0, arrange a plugin update promptly. CVE-2026-19907 lets an unauthenticated attacker impersonate an existing user, including an administrator, when the attacker knows the username. Wordfence assigns it CVSS 3.1 9.8 Critical in the CVE Program record.

What fails

The plugin’s authenticate_rest_user() function trusts a username parsed from LOGGED_IN_COOKIE without validating its cryptographic signature. Its route restriction can also be bypassed, so exposure is not confined to the plugin’s intended REST routes. The CNA describes REST API access with the impersonated user’s permissions, including creating another administrator.

The record lists disclosure at November 14, 2026, 00:33:13 UTC and CVE publication at 12:33:23 UTC that day. Its vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. These are disclosure and severity facts, not evidence of active exploitation.

Update status

The affected range is inclusive: 1.6 through 1.8.0. The CNA marks versions outside that range unaffected. The official WordPress directory offers 1.8.4 when checked on November 14, 2026. Its changelog lists general security improvements in 1.8.1 but does not name this CVE.

The CVE record references WordPress changeset 3701532 and a Wordfence advisory. Those pages could not be retrieved for this check, so the earliest fixed release has not been independently confirmed here. Do not interpret that limitation as a claim that no update exists.

Use the current supported release from the official distribution channel, and ask the developer or hosting provider to confirm its coverage of CVE-2026-19907. If you rely on a customized or provider-maintained package, obtain explicit backport confirmation for the installed build. Updating Linux or WordPress core alone does not replace Shipo’s plugin code.

Contain exposure and verify the store

Check the installed Shipo version and activation status in WordPress administration. Its plugin directory slug is shipo. Inventory every store you manage where it is active, including network-activated installations.

  1. Preserve a recoverable backup and coordinate the change with the store owner. Shipo supplies shipping and checkout features, so disabling it can interrupt orders or fulfillment. Decide how shipping will work during the interruption.
  2. If an update cannot be applied promptly, deactivate the affected plugin while arranging the replacement. Avoid deleting plugin data as a hurried workaround. Have the administrator verify the deactivation across affected sites.
  3. Test the supported update on a protected staging copy, then deploy it and confirm the installed version. Check shipping choices, checkout and shipment creation with the store’s approved test process before considering service restored.
  4. Review administrator accounts and recent role changes. Investigate unexpected accounts, unfamiliar privileged activity and changes to site code. Preserve relevant logs and backups before cleanup. An update does not remove an account or other persistence created before patching.

Restrict investigation to systems you administer. Do not test forged login cookies or account creation against a working store. A normal login or successful checkout does not demonstrate that the authentication bypass is fixed; use the maintainer’s security confirmation and an authorized validation process. If you find evidence of compromise, involve the hosting provider or incident-response team, then revoke unauthorized access and rotate affected credentials from a trusted system.

Inspect the public record from Linux

This example downloads public CVE metadata without contacting a WordPress site. It requires Bash, curl and Python 3. Create a scratch directory, and stop if setup fails. Keep the same terminal session for cleanup.

advisory_dir=$(mktemp -d ./shipo-advisory.XXXXXX) &&
cd -- "$advisory_dir"

Save this as inspect-shipo-record.py:

import json
from pathlib import Path
import sys

record = json.loads(Path(sys.argv[1]).read_text(encoding="utf-8"))
metadata = record["cveMetadata"]
if metadata["cveId"] != "CVE-2026-19907":
    raise SystemExit("Expected CVE-2026-19907")
cna = record["containers"]["cna"]
score = cna["metrics"][0]["cvssV3_1"]
print("CVE:", metadata["cveId"])
print("CNA:", metadata["assignerShortName"])
print("Published (UTC):", metadata["datePublished"])
for event in cna.get("timeline", []):
    if event["value"] == "Disclosed":
        print("Disclosed (UTC):", event["time"])
for product in cna["affected"]:
    for version in product["versions"]:
        if version["status"] == "affected":
            print("Affected:", version["version"], "through",
                  version["lessThanOrEqual"], "(inclusive)")
print("CVSS:", score["version"], score["baseScore"], score["baseSeverity"])
print("Metadata only; no WordPress site was inspected.")

Download the record and run the helper:

curl --fail --silent --show-error --max-time 30 \
  'https://cveawg.mitre.org/api/cve/CVE-2026-19907' \
  --output shipo-cve.json &&
python3 inspect-shipo-record.py shipo-cve.json

Actual output on Debian 13 with Python 3.12.14, November 14, 2026:

CVE: CVE-2026-19907
CNA: Wordfence
Published (UTC): 2026-11-14T12:33:23.699Z
Disclosed (UTC): 2026-11-14T00:33:13.000Z
Affected: 1.6 through 1.8.0 (inclusive)
CVSS: 3.1 9.8 CRITICAL
Metadata only; no WordPress site was inspected.

The helper expects this record’s current structure. It does not inspect an installed plugin or determine whether a site is compromised. Save the downloaded JSON and its retrieval date elsewhere if you need an incident record; the live CVE record can change.

From the scratch directory in the same terminal session, optional cleanup removes only the example files and their empty directory:

rm -- inspect-shipo-record.py shipo-cve.json &&
cd .. &&
rmdir -- "$advisory_dir" &&
unset advisory_dir

Setup and cleanup completed without output. No WordPress instance, plugin update, authentication bypass or incident-recovery procedure was tested for this article.

This post was created with assistance from AI.

Last updated on