WPify Woo <= 5.4.16 - Authenticated (Shop Manager+) Privilege Escalation via Arbitrary Option Update via save_option REST Endpoint
Strategic Overview
- Status
- Patched in 5.4.17
- Affected Version
<= 5.4.16- CVSS
- 8.0High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-12736
At a glance
CVE-2026-12736 is a high-severity Improper Privilege Management vulnerability in the WPify Woo WordPress plugin, affecting versions <= 5.4.16. It carries a CVSS score of 8.0 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Shop Manager level or above. The issue is fixed in version 5.4.17; sites on affected versions should update now. Disclosed July 2026, reported by Wordfence PRISM.
Vulnerability Overview
The Wpify Woo plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 5.4.16. This is due to the SettingsApi::save_option() REST route (POST /wp-json/wpify-woo/v1/option) passing the request-supplied 'option' and 'data' parameters directly to update_option() without any option-name allowlist or value sanitization, while the permission_callback only verifies the manage_woocommerce capability. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to elevate their privileges to Administrator by overwriting arbitrary WordPress options (for example setting default_role to administrator and users_can_register to 1, or disabling security plugins via active_plugins).
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-269: Improper Privilege Management
WPify Woo <= 5.4.16 carries this weakness at option, and reaching it takes an account at Shop Manager level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For WPify Woo the fix is 5.4.17: builds <= 5.4.16 are affected, anything from 5.4.17 onward is not.
Remediation
Update to version 5.4.17, 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: WPify Woo 5.4.17 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WPify Woo – Withdrawal, CRN/VAT, QR payments, Heureka and more for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C