SmartyParcel – Multi-Carrier Shipping, Order Tracking & Live Rates for WooCommerce <= 1.23.3 - Authenticated (Subscriber+) Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 1.23.4
- Affected Version
<= 1.23.3- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-84836
At a glance
CVE-2026-84836 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the SmartyParcel WordPress plugin, affecting versions <= 1.23.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.23.4; sites on affected versions should update now. Disclosed September 2026, reported by Nguyen Ba Khanh.
Vulnerability Overview
The SmartyParcel – Multi-Carrier Shipping, Order Tracking & Live Rates for WooCommerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.23.3. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.
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 interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in SmartyParcel <= 1.23.3 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For SmartyParcel the fix is 1.23.4: builds <= 1.23.3 are affected, anything from 1.23.4 onward is not.
Remediation
Update to version 1.23.4, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: SmartyParcel 1.23.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in SmartyParcel – DHL Express, GLS, InPost & Nova Post for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C