Overview
CVE-2025-52085 is a critical SQL Injection vulnerability discovered in the Yoosee application version 6.32.4. This vulnerability poses a significant threat to organizations and individuals who use the Yoosee application, as it allows an authenticated attacker to inject arbitrary SQL queries via a request to a backend API endpoint.
The implications of this vulnerability are severe, as successful exploitation leads to the extraction of sensitive database information. This extracted data can include the database server banner and version, the current database user and schema, the current DBMS user privileges, and arbitrary data from any table. Therefore, it is crucial for users and administrators of the Yoosee application to understand this vulnerability and implement appropriate mitigation measures.
Vulnerability Summary
CVE ID: CVE-2025-52085
Severity: High (8.8)
Attack Vector: Network
Privileges Required: Low
User Interaction: Required
Impact: Potential system compromise and data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
Yoosee Application | v6.32.4
How the Exploit Works
An attacker who has authenticated access to the Yoosee application can exploit this vulnerability by sending a specially crafted request to a specific backend API endpoint. This request contains arbitrary SQL queries that the application’s backend processes without proper sanitization or validation.
Once processed, these queries can return sensitive information from the application’s database. This information can include the database server banner and version, the current database user and schema, the current DBMS user privileges, and arbitrary data from any table. With this information, an attacker can potentially compromise the system or leak data.
Conceptual Example Code
Here is a conceptual example of an HTTP request that could exploit the vulnerability:
POST /api/vulnerable_endpoint HTTP/1.1
Host: target.example.com
Content-Type: application/json
Authorization: Bearer [user_token]
{
"user_id": "1; SELECT * FROM users;"
}In this example, the “user_id” parameter contains an SQL injection payload (“1; SELECT * FROM users;”). If the application fails to properly sanitize or validate this input, it could execute the SQL query, returning all data from the “users” table.