InPost PL <= 1.9.0 - Missing Authorization to Unauthenticated WooCommerce Order Parcel-Locker Hijacking
Strategic Overview
- Status
- Patched in 1.9.1
- Affected Plugin
- InPost PL
- Affected Version
<= 1.9.0- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-9702
At a glance
CVE-2026-9702 is a medium-severity Missing Authorization vulnerability in the InPost PL WordPress plugin, affecting versions <= 1.9.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.9.1; sites on affected versions should update now. Disclosed June 2026, reported by Pedro Pinho.
Vulnerability Overview
The InPost PL plugin for WordPress is vulnerable to unauthorized access in versions up to, and including, 1.9.0. This is due to missing order ownership verification in the update_locker_from_typ_page AJAX handler, which did not validate the order key before updating order meta. This makes it possible for unauthenticated attackers to hijack the parcel locker assignment on any WooCommerce order by supplying an arbitrary order ID, redirecting deliveries to an attacker-controlled locker.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in InPost PL <= 1.9.0 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For InPost PL the fix is 1.9.1: builds <= 1.9.0 are affected, anything from 1.9.1 onward is not.
Remediation
Update to version 1.9.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: InPost PL 1.9.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C