CVE-2026-10580

published 2026-06-05

CVE-2026-10580: The Hippoo Mobile App for WooCommerce plugin for WordPress is vulnerable to Authentication Bypass leading to Administrator Account Takeover in all versions up…

Priority P1 78 critical 9.8 CVSS 3.1

AV N AC L PR N UI N S U C H I H A H

EXPLOIT

The Hippoo Mobile App for WooCommerce plugin for WordPress is vulnerable to Authentication Bypass leading to Administrator Account Takeover in all versions up to and including 1.9.4. This is due to a logic conflation in HippooPermissions::get_user_permissions(), which returns the same null sentinel for both administrators and unauthenticated visitors — a value that HippooPermissions::has_role_access() unconditionally interprets as full administrator access — causing override_extension_permission_callback() to assign __return_true as the permission callback for every WordPress and WooCommerce REST route cloned under /wc-hippoo/v1/ext/ by HippooControllerWithAuth::re_register_external_routes(), while the block_unauthorized_access() pre-dispatch guard fails to block unauthenticated users for the same reason. This makes it possible for unauthenticated attackers to invoke any core REST endpoint without credentials — most critically, sending a POST request to /wc-hippoo/v1/ext/wp/v2/users/ with a {"password":""} body to reset the password of any WordPress user, including the site administrator, and gain full administrative control of the site.

Affected

1 ranges

Vendor	Product	Version range	Fixed in
hippooo	hippoo_mobile_app_for_woocommerce	<= 1.9.4	—

Detection & IOCs extracted from sources · hover to see the quote

url /wp-json/wc-hippoo/v1/ext/wp/v2/users/1↗

url /wc-hippoo/v1/ext/wp/v2/users/↗

path /wp-content/plugins/hippoo/readme.txt↗

command POST /wp-json/wc-hippoo/v1/ext/wp/v2/users/1 HTTP/1.1 Content-Type: application/json {"password":"<new_password>"}↗

• → Detect unauthenticated POST requests to the cloned WooCommerce REST route /wp-json/wc-hippoo/v1/ext/wp/v2/users/ — especially targeting user ID 1 (administrator) — with a JSON body containing a 'password' key and no Authorization header. ↗
• → Successful exploitation responses will contain the strings 'is_super_admin', 'capabilities', and 'woocommerce_meta' in the HTTP response body — use these as confirmation indicators. ↗
• → Reconnaissance phase: attackers may probe /wp-content/plugins/hippoo/readme.txt to confirm the vulnerable plugin version (≤ 1.9.4) is installed before launching the exploit. ↗
• → All REST routes cloned under /wc-hippoo/v1/ext/ are affected — monitor for any unauthenticated requests to this path prefix, not just the users endpoint. ↗
• → Use the Shodan query 'http.component:"wordpress"' and FOFA query 'body="hippoo"' to identify potentially exposed instances for proactive scanning. ↗

• · The vulnerability affects all plugin versions up to and including 1.9.4. Confirm the installed version via readme.txt before treating a target as vulnerable. ↗
• · The exploit hardcodes user ID 1 in the PoC template, but the vulnerability allows password reset of ANY WordPress user — detection rules should match /wc-hippoo/v1/ext/wp/v2/users/<any_id>, not just /users/1. ↗
• · The root cause is a logic conflation in HippooPermissions::get_user_permissions() returning null for both admins and unauthenticated visitors, and HippooPermissions::has_role_access() unconditionally treating null as full admin — patching requires fixing both functions. ↗

CVEs like this are exactly what “Exploited This Week” covers.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.

CWE-285