CVE-2025-14696
Weak Password Recovery Vulnerability in Sixun Shanghui API
Publication date: 2025-12-15
Last updated on: 2025-12-15
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| shenzhen_sixun_software | sissyun_shanghui_group_business_management_system | 4.10.24.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-640 | The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-14696 is an unauthorized password modification vulnerability in Shenzhen Sixun Software's Sissyun Shanghui Group Business Management System 4.10.24.3. It exists in the API endpoint /api/GylOperator/UpdatePasswordBatch, which allows attackers to reset or change user passwords without proper authorization or knowing the original password. Attackers can enumerate user IDs and send POST requests to update passwords arbitrarily, bypassing authentication and authorization checks. This leads to weak password recovery and unauthorized access to user accounts. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to gain unauthorized access to user accounts by resetting passwords without needing the original credentials. As a result, attackers can take full control of affected accounts, potentially leading to data breaches, unauthorized actions within the system, and compromise of system integrity. Since the exploit is publicly available and can be executed remotely without authentication, it poses a significant security risk to users and organizations relying on the affected system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unauthorized POST requests to the API endpoint `/api/GylOperator/UpdatePasswordBatch` that include parameters such as `entity[OperId]`, `entity[Password]`, and `entity[OriginalPwd]`. An example detection method is to look for POST requests attempting to reset passwords without proper authorization, especially those with `entity[RequiredOriginalPwd]=false`. Network monitoring tools or web server logs can be used to identify such suspicious requests. For example, using curl to test the endpoint with crafted parameters can help verify if the system is vulnerable: ```curl -X POST http://<target>/api/GylOperator/UpdatePasswordBatch -d 'entity[OperId]=01001&entity[Password]=01001&entity[OriginalPwd]=01001&entity[RoleIds]=1&entity[RequiredOriginalPwd]=false' -H 'Content-Type: application/x-www-form-urlencoded'``` If this request succeeds in changing a password without authentication, the system is vulnerable. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable API endpoint `/api/GylOperator/UpdatePasswordBatch` by implementing proper authentication and authorization checks to prevent unauthorized password resets. If possible, disable or restrict the password batch update functionality until a patch or fix is available. Monitoring and logging all access to this endpoint for suspicious activity is also recommended. Since no official patch or vendor response is available, consider replacing the affected product or deploying compensating controls such as web application firewalls (WAF) to block unauthorized requests targeting this API. [3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized password recovery and modification without authentication, compromising account security and system integrity. This weakness in password recovery mechanisms can lead to unauthorized access to user accounts and potentially sensitive data, which may result in non-compliance with common standards and regulations such as GDPR and HIPAA that require strong access controls and protection of personal data. However, specific impacts on compliance are not detailed in the provided resources. [1, 2, 3]