# CVE-2026-10580: Auth bypass in Hippoo Mobile App for WooCommerce

> Unauthenticated attackers can bypass authentication to reset administrator passwords and gain full control of the WordPress site via the REST API.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2026
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-5xvj-rcr9-wm4h

## What is CVE-2026-10580?

CVE-2026-10580 is a critical authentication bypass vulnerability in hippooo Hippoo Mobile App for WooCommerce, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-10580?


## How do I fix CVE-2026-10580?

No fix has been published for CVE-2026-10580 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10580 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10580 exists.

Public exploit code:

- Hippoo Mobile App for WooCommerce <= 1.9.4 - Unauthenticated Authentication Bypass to Administrator Account Takeover (github_poc): https://github.com/Polosss/By-Poloss..-..CVE-2026-10580
- PoC exploit for CVE-2026-10580 - Authentication Bypass in Hippoo Mobile App for WooCommerce <= 1.9.4 leading to Admin Account Takeover (github_poc): https://github.com/0xgh057r3c0n/CVE-2026-10580
- Hippoo Mobile App for WooCommerce <= 1.9.4 - Authentication Bypass to Admin Account Takeover (nuclei): http/cves/2026/CVE-2026-10580.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10580 and fix it if it is affected.

What it is: CVE-2026-10580 is a critical authentication bypass vulnerability in hippooo Hippoo Mobile App for WooCommerce, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10580 exists.

Affected product: hippooo Hippoo Mobile App for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10580/ (Markdown: https://insights.sbomify.com/CVE-2026-10580/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10580
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10580
- OSV: https://osv.dev/vulnerability/CVE-2026-10580

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10580/
Summaries are generated and may contain mistakes; the official description above is the record.