dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-10580

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Hippoo plugin has an authentication bypass where HippooPermissions::get_user_permissions() returns the same null value for both unauthenticated visitors and administrators. The has_role_access() method unconditionally interprets this null as full admin access, causing __return_true to be assigned as the permission callback for all /wc-hippoo/v1/ext/ REST routes. This allows unauthenticated attackers to reset any user password, including administrator accounts, via the wp/v2/users endpoint.

MitigationUpdate the Hippoo Mobile App for WooCommerce plugin to version 1.9.5 or later once available, or implement a code fix that ensures get_user_permissions() correctly distinguishes between unauthenticated users (null/empty) and administrator role, preventing unauthenticated access to REST endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Hippoo plugin installation
    Check the WordPress plugins directory for the Hippoo Mobile App for WooCommerce plugin file, or query the /wp-json/wp/v2/plugins endpoint if accessible, to retrieve the installed version
    Affected if The Hippoo plugin is installed and the version is lower than 1.9.5 or the version cannot be determined
  2. Verify vulnerable REST routes exist
    Send a GET request to /wp-json/wc-hippoo/v1/ext/permissions (or any /wc-hippoo/v1/ext/ route) without providing any authentication credentials (no cookies, no Authorization header)
    Affected if The endpoint returns a successful response instead of a 401 Unauthorized or 403 Forbidden error, indicating the permission callback is set to __return_true
  3. Test unauthenticated user password reset access
    Send a POST request to /wp-json/wp/v2/users/{user_id} with a password_reset payload (such as {"password": "newpassword123"}), omitting any authentication headers
    Affected if The request succeeds with a 200 OK response, allowing password modification without being logged in, which confirms the authentication bypass is active
  4. Inspect permission callback in code
    Locate the HippooPermissions class file (typically in /wp-content/plugins/hippoo-mobile-app-for-woocommerce/includes/ or similar) and examine the has_role_access() method to confirm it assigns __return_true when get_user_permissions() returns null
    Affected if The code shows that null permission results are treated as admin-level access rather than being rejected

A user is affected if the Hippoo plugin version is below 1.9.5 AND the /wc-hippoo/v1/ext/ REST endpoints are accessible without authentication, allowing unauthenticated password resets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Hippoo Mobile App for WooCommerce plugin to version 1.9.5 or later once available, or implement a code fix that ensures get_user_permissions() correctly distinguishes between unauthenticated users (null/empty) and administrator role, preventing unauthenticated access to REST endpoints.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version higher than 1.9.4)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Hippoo Mobile App for WooCommerce plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, delete the current plugin and reinstall the latest version from the WordPress plugin repository
  6. After updating, verify the site still functions correctly
  7. Check that the REST API endpoints under /wc-hippoo/v1/ext/ are no longer accessible without authentication

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10580 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10580 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data