fixnx
highCVE-2026-12736

WPify Woo <= 5.4.16 - Authenticated (Shop Manager+) Privilege Escalation via Arbitrary Option Update via save_option REST Endpoint

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

Browse WordPress security risks
ProductWPify Woo – Withdrawal, CRN/VAT, QR payments, Heureka and more for WooCommerce
CVSS8.0
EPSSNot scored yet
UpdatedJuly 24, 2026

Quick answer

WPify Woo – Withdrawal, CRN/VAT, QR payments, Heureka and more for WooCommerce should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • <= 5.4.16
  • up to and including 5.4.16

Fixed versions

  • 5.4.17

How to fix it

CVE-2026-12736 affects WPify Woo – Withdrawal, CRN/VAT, QR payments, Heureka and more for WooCommerce and involves authorization failure. Successful exploitation may let a lower-privileged user view or change data outside their allowed scope. Prioritize internet-facing, privileged, automation, and production deployments. Upgrade WPify Woo – Withdrawal, CRN/VAT, QR payments, Heureka and more for WooCommerce to 5.4.17 or a later vendor-supported fixed release.

  1. Inventory every deployment, device, package, plugin, container, build, and environment that uses WPify Woo – Withdrawal, CRN/VAT, QR payments, Heureka and more for WooCommerce.
  2. Compare the installed version with the recorded affected range: <= 5.4.16, *-5.4.16.
  3. Upgrade WPify Woo – Withdrawal, CRN/VAT, QR payments, Heureka and more for WooCommerce to 5.4.17 or a later vendor-supported fixed release.
  4. Until patched, disable the affected WPify Woo – Withdrawal, CRN/VAT, QR payments, Heureka and more for WooCommerce feature or plugin and restrict its public and administrator endpoints.
  5. Review configuration, roles, tokens, network paths, and exposed endpoints connected to WPify Woo – Withdrawal, CRN/VAT, QR payments, Heureka and more for WooCommerce; remove access that is not required.
  6. Review authentication, API, audit, and object-change logs for cross-user access, bypassed checks, or unexpected privileged actions.
  7. If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-12736 in place.
  • Use a safe regression test to confirm the affected authorization failure path no longer produces the vulnerable behavior.
  • Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
  • Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
  • Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.

Related categories

WordPressWooCommercePrivilege Escalation

Related security risks

More published guidance from the same primary category.

high

WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 43.2 - Cross-Site Request Forgery to Privilege Escalation via Plugin Settings Update

Updated July 24, 2026

medium

Payment Plugins for Stripe WooCommerce <= 4.0.7 - Missing Authorization to Unauthenticated Arbitrary Order Status Modification via Empty Webhook Secret

Updated July 24, 2026

medium

CVE-2026-65475 Modula Image Gallery vulnerability

Updated July 24, 2026

Trusted references

Source advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceWordfence advisoryNVD, WordfenceWordfence advisoryNVD, Wordfence

FAQ

What is affected by CVE-2026-12736?

WPify Woo – Withdrawal, CRN/VAT, QR payments, Heureka and more for WooCommerce versions listed as affected should be reviewed: <= 5.4.16, up to and including 5.4.16.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.