Privilege Escalation in Wpify Woo (WordPress plugin) (CVE-2026-12736)
Summary
Vulnerability in Wpify Woo (WordPress plugin) (CVE-2026-12736). Successful exploitation can lead to full system takeover. Exploitable via POST /wp-json/wpify-woo/v1/option.
Original description
The description as published by the source.
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).
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-12736 has been found in Wpify Woo (WordPress plugin).
Attackers can target a specific entry point like POST /wp-json/wpify-woo/v1/option over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Wpify Woo (WordPress plugin) CVE-2026-12736" on the vendor's site.
CVE-2026-12736 (Wpify Woo (WordPress plugin)) — CWE-269 / CVSS v3 8.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /wp-json/wpify-woo/v1/option
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-269) exists in Wpify Woo (WordPress plugin). Attackers reach the vulnerable code path via POST /wp-json/wpify-woo/v1/option.
Check the vendor advisory for the affected versions of Wpify Woo (WordPress plugin). Attack surface: POST /wp-json/wpify-woo/v1/option.
Severity: High (CVSS 8.0/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /wp-json/wpify-woo/v1/option requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Wpify Woo (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /wp-json/wpify-woo/v1/option' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /wp-json/wpify-woo/v1/optionへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /wp-json/wpify-woo/v1/option on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。