ShipWorks Connector for Woocommerce <= 5.2.5 - Cross-Site Request Forgery to Service Password/Username Update
Strategic Overview
- Status
- Patched in 5.2.6
- Affected Plugin
- ShipWorks Connector for Woocommerce
- Affected Version
<= 5.2.5- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-13317
At a glance
CVE-2024-13317 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the ShipWorks Connector for Woocommerce WordPress plugin, affecting versions <= 5.2.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.2.6; sites on affected versions should update now. Disclosed January 2025, reported by SOPROBRO.
Vulnerability Overview
The ShipWorks Connector for Woocommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.2.5. This is due to missing or incorrect nonce validation on the 'shipworks-wordpress' page. This makes it possible for unauthenticated attackers to update the services username and password via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
ShipWorks Connector for Woocommerce <= 5.2.5 carries this weakness at shipworks-wordpress, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For ShipWorks Connector for Woocommerce the fix is 5.2.6: builds <= 5.2.5 are affected, anything from 5.2.6 onward is not.
Remediation
Update to version 5.2.6, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to ShipWorks Connector for Woocommerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: ShipWorks Connector for Woocommerce 5.2.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C