WooCommerce Order Proposal <= 2.0.5 - Authenticated (Shop Manager+) Privilege Escalation via Order Proposal
Strategic Overview
- Status
- Patched in 2.0.6
- Affected Plugin
- WooCommerce Order Proposal
- Affected Version
<= 2.0.5- CVSS
- 7.2High
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2024-9927
At a glance
CVE-2024-9927 is a high-severity Improper Authentication vulnerability in the WooCommerce Order Proposal WordPress plugin, affecting versions <= 2.0.5. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Shop Manager level or above. The issue is fixed in version 2.0.6; sites on affected versions should update now. Disclosed October 2024, reported by theop.
Vulnerability Overview
The WooCommerce Order Proposal plugin for WordPress is vulnerable to privilege escalation via order proposal in all versions up to and including 2.0.5. This is due to the improper implementation of allow_payment_without_login function. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to log in to WordPress as an arbitrary user account, including administrators.
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 confidentiality, integrity, availability — full site compromise territory.
CWE-287: Improper Authentication
Reaching this weakness in WooCommerce Order Proposal <= 2.0.5 takes an account at Shop Manager level or above. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For WooCommerce Order Proposal the fix is 2.0.6: builds <= 2.0.5 are affected, anything from 2.0.6 onward is not.
Remediation
Update to version 2.0.6, 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: WooCommerce Order Proposal 2.0.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C