WordPress security changelog
HIGH CVE-2026-12736 Deferred

WPify Woo lets Shop Managers overwrite arbitrary WordPress options

WPify Woo through 5.4.16 grants its POST /wp-json/wpify-woo/v1/option route to users with manage_woocommerce. SettingsApi::save_option() passes the request-controlled option, data and optional autoload values directly to update_option() without an option-name allowlist. A Shop Manager can therefore change security-sensitive core options, enable administrator registration or disable security plugins and escalate privileges.

CVE / CNA score 8.0 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
WPify Woo – Withdrawal, CRN/VAT, QR payments, Heureka and more for WooCommerce
Plugin slug
wpify-woo
Affected
<= 5.4.16
Safe version
5.4.17
Published
Jul 24, 2026
Weakness
CWE-269 — Improper Privilege Management

This CVE was published Jul 24, 2026 and is one of 3 known issues for this plugin.

What to do

Update, patch or deactivate.

Update WPify Woo to 5.4.17 or later; that release removes the dangerous REST route and callback. If an immediate update is impossible, remove the route registration or change its permission callback to manage_options and allow only documented WPify option names. Review core registration, default-role and active-plugin options for unauthorized changes.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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).

CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

References

Primary and upstream sources