dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12655

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 arbitrary file write via a missing authorization check in all versions up to, and including, 1.7.1. This is due to the REST API endpoint `/wp-json/hippoo/v1/wc/token/save_callback/{token_id}` being registered with `permission_callback => '__return_true'`, which allows unauthenticated access. This makes it possible for unauthenticated attackers to write arbitrary JSON content to the server's publicly accessible upload directory via the vulnerable endpoint.

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 Mobile App for WooCommerce plugin registers a REST API endpoint at /wp-json/hippoo/v1/wc/token/save_callback/{token_id} with permission_callback set to '__return_true', bypassing all authentication. This allows any unauthenticated user to write arbitrary JSON content to the publicly accessible WordPress upload directory, potentially enabling remote code execution if writable file types are permitted.

MitigationUpdate the plugin to version 1.7.2 or later which contains the authorization fix; until then, consider disabling the plugin or blocking the /wp-json/hippoo/ endpoints at the web server level.

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
None
Integrity
Low
Availability
None

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

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. Verify Hippoo plugin is installed
    Check the WordPress plugin directory for the Hippoo Mobile App for WooCommerce plugin folder. In the WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Hippoo Mobile App for WooCommerce' in the list.
    Affected if The plugin appears in the installed plugins list and is active.
  2. Check the installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, find the Hippoo plugin and note the version number displayed below the plugin name. Compare this version against the fixed version 1.7.2.
    Affected if The installed version is lower than 1.7.2.
  3. Identify if the vulnerable REST API route exists
    Access the WordPress REST API endpoint at /wp-json/hippoo/v1/wc/token/save_callback/1 (or any numeric ID). Use a tool like curl to send a GET request without any authentication headers: curl -s https://yourdomain.com/wp-json/hippoo/v1/wc/token/save_callback/1
    Affected if The endpoint returns a response (rather than a 401/403 authentication error), indicating the route is registered and publicly accessible.
  4. Inspect the plugin source code for the vulnerable permission_callback
    Locate the plugin file that registers the REST route, typically in the main plugin PHP file or an includes/rest-api.php file. Search for 'save_callback' and examine the permission_callback parameter. If it is set to '__return_true', the vulnerability is present.
    Affected if The code shows permission_callback set to '__return_true' for the /save_callback/ route.

If the Hippoo plugin is installed, version is below 1.7.2, and the /wp-json/hippoo/v1/wc/token/save_callback/ endpoint responds without authentication, the environment is affected by this CVE.

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 plugin to version 1.7.2 or later which contains the authorization fix; until then, consider disabling the plugin or blocking the /wp-json/hippoo/ endpoints at the web server level.

Recommended fix Moderate confidence

1.7.2 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Hippoo Mobile App for WooCommerce plugin
  4. Check if an update is available and update to the latest version (1.7.2 or later)
  5. Alternatively, download the latest version from the WordPress plugin repository and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12655 — 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-2025-12655 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