Custom Order Numbers for WooCommerce <= 1.4.0 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.4.1
- Affected Plugin
- Custom Order Numbers for WooCommerce
- Affected Version
<= 1.4.0- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-45367
At a glance
CVE-2022-45367 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Custom Order Numbers for WooCommerce WordPress plugin, affecting versions <= 1.4.0. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.4.1; sites on affected versions should update now. Disclosed April 2023, reported by Muhammad Daffa.
Vulnerability Overview
The Custom Order Numbers for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.4.0. This is due to missing nonce validation on several functions like alg_custom_order_numbers_admin_notice_dismiss, alg_custom_order_numbers_admin_meta_key_notice_dismiss, and save_order_number_meta_box to name a few. This makes it possible for unauthenticated attackers to perform unauthorized actions like dismissing notices and reordering metaboxes 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)
Reaching this weakness in Custom Order Numbers for WooCommerce <= 1.4.0 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 Custom Order Numbers for WooCommerce the fix is 1.4.1: builds <= 1.4.0 are affected, anything from 1.4.1 onward is not.
Remediation
Update to version 1.4.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Custom Order Numbers for WooCommerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Custom Order Numbers for WooCommerce 1.4.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Custom Order Numbers for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C