Shipo 1.6 to 1.8.0: REST cookie authentication bypass allows administrator impersonation (CVE-2026-19907)
Identifiers: CVE-2026-19907
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
On 14 November 2026 Wordfence disclosed CVE-2026-19907 in the Shipo WooCommerce courier plugin. In versions 1.6 through 1.8.0, the plugin's REST authentication accepts a cookie-supplied identity without a cryptographic signature. The plugin intends to apply this only to its own REST routes, but the researcher states that restriction can be bypassed, so the forged identity can be accepted on an unrelated REST endpoint. An unauthenticated attacker who knows an existing username on the site can act as that user, including an administrator, and may create accounts. The vendor fixed this in 1.8.1; the current release is 1.8.4.
Impact
An attacker acting as an administrator controls the whole site: settings, plugins, content, and customer order data. Persistence such as extra admin accounts or planted files can survive a later update. This is a plugin-specific authentication flaw in Shipo, not a bug in WordPress core. Because the researcher states the intended route restriction can be bypassed, the impersonation is not confined to Shipo's own REST routes.
Who is affected
Public WooCommerce stores with Shipo active at 1.6 through 1.8.0 and a reachable WordPress REST API. The attacker must know an existing username on the site. How easily a username can be obtained varies by site and was not verified for this briefing. Sites already on 1.8.1 or newer are not affected by this issue as described.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| Shipo | 1.6 through 1.8.0 | 1.8.1 |
Exploitation evidence
Exploitation not established. No exploitation in the wild is established in reviewed Wordfence, vendor, or KEV sources as of 14 November 2026. The prerequisites are an active Shipo install in the affected range, a reachable REST API, and knowledge of an existing username. No authentication is required. Technical exploitation details are deliberately not reproduced here.
Actions
- Update Shipo to 1.8.1 or newer (vendor current 1.8.4) through the normal WordPress update flow.
- Confirm the active plugin version on the Plugins screen after updating.
- Test the courier and checkout flow (rates, locker selection, shipment creation) using a controlled test order on your own store, without a real customer's data, a real payment, or a purchased label.
- If you have reason to suspect compromise, review Users for unexpected administrator accounts, recent logins, and unfamiliar plugin or file changes. The update does not remove a backdoor already placed. Plan a bounded recovery: rotate admin passwords and API keys, remove unknown accounts, restore from a known-good backup if needed.
- If you cannot update now, deactivate Shipo until you can and ask your hosting or WordPress provider about interim options. No firewall or configuration rule has been verified as equivalent to the vendor fix.
Unknowns
- The affected range and the technical description rest primarily on Wordfence. The vendor's 1.8.1 changelog says only "general improvements to plugin security", which confirms a release described as security hardening exists but does not independently confirm the fix or the precise versions.
- The CVE record at the CNA returned 404 and the WordPress.org Trac changeset returned 403 at check time. These are coverage gaps, not contradicting evidence.
- No in-the-wild exploitation was found in reviewed Wordfence, vendor, or CISA KEV sources. Absence of a report is not proof that none has occurred.
Sources
- Wordfence Intelligence https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/shipo/shipo-16-180-authentication-bypass-to-administrator
- Plugin vendor via WordPress.org SVN https://plugins.svn.wordpress.org/shipo/trunk/readme.txt
- CISA https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
Change history
- — Published: 14 November 2026: briefing created from the Wordfence disclosure of CVE-2026-19907 in Shipo. Affected 1.6 through 1.8.0, fixed in 1.8.1, vendor current 1.8.4. No exploitation established.