Ameeba Security Research

Defensive CVE and exploit intelligence

Ameeba Blog Search
TRENDING · 1 WEEK
Attack Vector
Vendor
Severity

CVE-2025-56161: Unauthorized Information Disclosure via YOSHOP 2.0 API

Views: 21

Overview

The vulnerability, CVE-2025-56161, is a significant cybersecurity threat affecting YOSHOP 2.0. The exploit allows unauthenticated users to disclose sensitive information via comment-list API endpoints in the Goods module. As a result, crucial user data, such as bcrypt password hash, mobile number, pay_money, and expend_money, are exposed in JSON responses, leading to potential system compromise or data leakage.

Vulnerability Summary

CVE ID: CVE-2025-56161
Severity: High (7.5)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Unauthorized disclosure of information, potential system compromise, and data leakage

Affected Products

Ameeba Chat Icon 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

YOSHOP | 2.0

How the Exploit Works

The vulnerability resides in the comment-list API endpoints in the Goods module of YOSHOP 2.0. The Comment model eagerly loads the related User model without any field filtering. As the User.php defines no $hidden or $visible attributes, sensitive fields like bcrypt password hash, mobile number, pay_money, and expend_money are exposed in JSON responses. This information can be accessed without authentication, leading to significant data leakage risk.

Conceptual Example Code

A potential exploit could involve a simple HTTP request to the vulnerable endpoint as shown below:

GET /api/goods.pinglun/list HTTP/1.1
Host: target.example.com
Content-Type: application/json

The server would then reply with a JSON response containing the sensitive user information.

Mitigation

YOSHOP users are advised to apply the latest vendor patches as soon as they are available. As a temporary mitigation, users can employ Web Application Firewall (WAF) or Intrusion Detection System (IDS) to monitor and block any suspicious activities. It’s also recommended to review the codebase and add necessary field filtering or data hiding mechanisms to protect sensitive fields in the User model.

Want to discuss this further? Join the Ameeba Cybersecurity Group Chat.

Disclaimer:

The information and code presented in this article are provided for educational and defensive cybersecurity purposes only. Any conceptual or pseudocode examples are simplified representations intended to raise awareness and promote secure development and system configuration practices.

Do not use this information to attempt unauthorized access or exploit vulnerabilities on systems that you do not own or have explicit permission to test.

Ameeba and its authors do not endorse or condone malicious behavior and are not responsible for misuse of the content. Always follow ethical hacking guidelines, responsible disclosure practices, and local laws.

More posts

Ameeba Chat