Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12655: CWE-862 Missing Authorization in hippooo Hippoo Mobile App for WooCommerce

0
Medium
VulnerabilityCVE-2025-12655cvecve-2025-12655cwe-862
Published: Fri Dec 12 2025 (12/12/2025, 06:32:58 UTC)
Source: CVE Database V5
Vendor/Project: hippooo
Product: Hippoo Mobile App for WooCommerce

Description

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.

AI-Powered Analysis

AILast updated: 12/12/2025, 07:18:09 UTC

Technical Analysis

CVE-2025-12655 is a vulnerability classified under CWE-862 (Missing Authorization) affecting the Hippoo Mobile App for WooCommerce plugin for WordPress. The root cause is the REST API endpoint `/wp-json/hippoo/v1/wc/token/save_callback/{token_id}` being registered with a permission callback set to `__return_true`, effectively disabling any authorization checks. This misconfiguration allows unauthenticated attackers to invoke the endpoint and write arbitrary JSON content to the server's upload directory, which is publicly accessible. Since the upload directory is exposed, attackers can potentially upload malicious files disguised as JSON, which could be leveraged for further attacks such as injecting malicious scripts or webshells, leading to integrity compromise of the website. The vulnerability affects all versions up to and including 1.7.1 of the plugin. The CVSS 3.1 base score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges required, no user interaction, and impact limited to integrity. No patches or exploit code are currently publicly available, but the vulnerability's nature makes it relatively easy to exploit. The plugin is used in WooCommerce-based e-commerce sites, which are prevalent in Europe, increasing the potential attack surface. The vulnerability does not directly affect confidentiality or availability but poses a significant risk to data integrity and site trustworthiness.

Potential Impact

For European organizations, especially e-commerce businesses relying on WooCommerce and the Hippoo Mobile App plugin, this vulnerability can lead to unauthorized modification of website content or injection of malicious payloads. This compromises the integrity of the web platform, potentially damaging brand reputation and customer trust. Attackers could use the arbitrary file write to deploy webshells, facilitating further attacks such as data theft, site defacement, or pivoting within the network. Since WooCommerce powers a significant portion of European online stores, the risk extends to financial losses, regulatory non-compliance (e.g., GDPR if customer data is indirectly affected), and operational disruptions. The vulnerability's exploitation does not require authentication or user interaction, increasing the likelihood of automated attacks. Organizations with limited security monitoring or outdated plugins are particularly vulnerable. The impact is more pronounced in countries with large e-commerce markets and high WooCommerce adoption, where attackers may find more lucrative targets.

Mitigation Recommendations

1. Immediately update the Hippoo Mobile App for WooCommerce plugin to a version that addresses this vulnerability once available. 2. In the absence of an official patch, restrict access to the vulnerable REST API endpoint by implementing web application firewall (WAF) rules that block unauthenticated requests to `/wp-json/hippoo/v1/wc/token/save_callback/*`. 3. Harden REST API permissions by customizing the permission_callback to enforce proper authorization checks, ensuring only authenticated and authorized users can access sensitive endpoints. 4. Monitor the upload directories for unusual or unexpected JSON files and remove any suspicious files promptly. 5. Employ file integrity monitoring to detect unauthorized changes to web-accessible directories. 6. Limit the permissions of the web server user to prevent execution of uploaded files and restrict write access to only necessary directories. 7. Conduct regular security audits and vulnerability scans focusing on WordPress plugins and REST API endpoints. 8. Educate development and operations teams about secure plugin configuration and the risks of exposing REST API endpoints without proper authorization.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-03T20:38:38.858Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693bbde4e6d9263eb3549376

Added to database: 12/12/2025, 7:01:56 AM

Last enriched: 12/12/2025, 7:18:09 AM

Last updated: 12/15/2025, 2:19:08 AM

Views: 22

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats