Overview
The CVE-2025-50902 vulnerability is a severe Cross-Site Request Forgery (CSRF) flaw found in the old-peanut Open-Shop, known also as old-peanut/wechat_applet__open_source, up to version 1.0.0. CSRF vulnerabilities allow attackers to manipulate victims into performing actions they do not intend to do, potentially leading to data leakage or system compromise. This vulnerability is of particular concern to businesses and individuals using this software for their e-commerce activities, as it could lead to unauthorized access and manipulation of sensitive data.
Vulnerability Summary
CVE ID: CVE-2025-50902
Severity: High (8.8 CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: Required
Impact: Potential system compromise or data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
old-peanut Open-Shop (old-peanut/wechat_applet__open_source) | Up to version 1.0.0
How the Exploit Works
The vulnerability is exploited when an attacker crafts a specific HTTP Post message and then tricks a victim into sending this request. The attacker can create a malicious website or email that, when interacted with by the user, sends the crafted HTTP Post request to the vulnerable old-peanut Open-Shop. The server, failing to validate the origin of the request, executes it as if it were a legitimate user action. This flaw allows the attacker to gain unauthorized access to sensitive information.
Conceptual Example Code
A conceptual exploit might look like this:
POST /vulnerable/endpoint HTTP/1.1
Host: target.example.com
Content-Type: application/json
{
"csrf_token": "stolen_token",
"action": "retrieve_user_data"
}In this example, the attacker crafts a malicious HTTP POST request using a stolen CSRF token. The action set in the request body instructs the server to retrieve user data, which is then sent back to the attacker.
Mitigation
Users can mitigate the risk of this vulnerability by applying the vendor patch as soon as it is available. In the meantime, they can use a Web Application Firewall (WAF) or Intrusion Detection System (IDS) as a temporary mitigation measure. These systems can be configured to detect and block CSRF attacks by identifying and blocking suspicious HTTP requests.