Advanced Shipment Tracking for WooCommerce <= 3.2.6 - Authenticated WordPress Options Change
Strategic Overview
- Status
- Patched in 3.2.7
- Affected Plugin
- Advanced Shipment Tracking for WooCommerce
- Affected Version
<= 3.2.6- CVSS
- 9.9Critical
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2021-4347
At a glance
CVE-2021-4347 is a critical-severity Missing Authorization vulnerability in the Advanced Shipment Tracking for WooCommerce WordPress plugin, affecting versions <= 3.2.6. It carries a CVSS score of 9.9 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 3.2.7; sites on affected versions should update now. Disclosed July 2021, reported by Jerome Bruandet.
Vulnerability Overview
The function update_shipment_status_email_status_fun in the plugin Advanced Shipment Tracking for WooCommerce in versions up to 3.2.6 is vulnerable to authenticated arbitrary options update. The function allows attackers (including those at customer level) to update any WordPress option in the database. Version 3.2.5 was initially released as a fix, but doesn't fully address the issue.
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. A successful exploit has high impact on integrity, availability.
CWE-862: Missing Authorization
Reaching this weakness in Advanced Shipment Tracking for WooCommerce <= 3.2.6 takes any authenticated account. 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 Advanced Shipment Tracking for WooCommerce the fix is 3.2.7: builds <= 3.2.6 are affected, anything from 3.2.7 onward is not.
Remediation
Update to version 3.2.7, 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: Advanced Shipment Tracking for WooCommerce 3.2.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Advanced Shipment Tracking for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C