Skip to main content
Mallory
Critical

Authentication Bypass and Administrator Account Takeover in Hippoo Mobile App for WooCommerce

IdentifiersCVE-2026-10580CWE-285· Improper Authorization

CVE-2026-10580 affects the Hippoo Mobile App for WooCommerce plugin for WordPress in all versions up to and including 1.9.4. The flaw is caused by authorization logic in HippooPermissions::get_user_permissions() and HippooPermissions::has_role_access(). Specifically, get_user_permissions() returns the same null sentinel value for both administrators and unauthenticated visitors, and has_role_access() incorrectly interprets that value as full administrator access. As a result, when HippooControllerWithAuth::re_register_external_routes() clones WordPress and WooCommerce REST routes under /wc-hippoo/v1/ext/, override_extension_permission_callback() assigns __return_true as the permission callback for those routes. The related block_unauthorized_access() pre-dispatch guard also fails to stop unauthenticated requests for the same reason. This exposes cloned core REST endpoints to unauthenticated access. The most critical documented exploitation path is sending a POST request to /wc-hippoo/v1/ext/wp/v2/users/<id> with a JSON body such as {"password":"<new_password>"}, allowing an attacker to reset the password of any WordPress user, including an administrator.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthenticated attackers to bypass authorization on cloned WordPress and WooCommerce REST API routes exposed under /wc-hippoo/v1/ext/. This can be used to invoke privileged core REST functionality without credentials. The documented high-impact outcome is arbitrary password reset for any WordPress account, including administrator accounts, resulting in administrator account takeover and full administrative control of the affected WordPress site. Given the exposed access to cloned core REST endpoints, the vulnerability may also enable unauthorized modification of site data and other actions normally restricted to authenticated privileged users.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable or uninstall the Hippoo Mobile App for WooCommerce plugin. Where operationally feasible, restrict external access to the affected /wc-hippoo/v1/ext/ REST paths via web server, WAF, reverse proxy, or network ACL controls. Monitor for suspicious unauthenticated requests to cloned REST endpoints, especially POST requests to /wc-hippoo/v1/ext/wp/v2/users/<id> and other user-management routes, and review for unauthorized password changes or account modifications.

Remediation

Patch, then assume compromise.

Upgrade the Hippoo Mobile App for WooCommerce plugin to a fixed version once available. The provided content states that all versions up to and including 1.9.4 are vulnerable. If a patched release is not available, remove or disable the plugin immediately. The referenced WordPress plugin changeset 3557733 should be reviewed to identify the vendor fix and corresponding remediated version.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.

VALID 0 / 2 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.