Overview
CVE-2025-46740 is a significant security vulnerability that allows an authenticated user without administrative privileges to change the administrator Account Name. This vulnerability impacts any system or software that does not properly limit the account name changes to the appropriate user roles, potentially leading to system compromise or data leakage. The severity of this issue is underlined by its CVSS Severity Score of 7.5, indicating a high risk to affected systems.
Vulnerability Summary
CVE ID: CVE-2025-46740
Severity: High (7.5)
Attack Vector: Network
Privileges Required: Low
User Interaction: Required
Impact: Unauthorised Administrative Account Name Change, which could lead to system compromise or 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
Product 1 | Version 1, Version 2
Product 2 | Version 3, Version 4
How the Exploit Works
The vulnerability exists within the account management functionality of the affected software. An authenticated user without administrative permissions can exploit this issue by manipulating the request sent to the server to change the account name. If successful, the attacker could change the administrator account name, potentially disrupting the system’s operations or gaining unauthorized access.
Conceptual Example Code
Here is an illustrative example of how the vulnerability might be exploited using a HTTP POST request:
POST /changeAccountName HTTP/1.1
Host: target.example.com
Content-Type: application/json
Authorization: Bearer user_token_without_admin_permissions
{
"accountName": "admin",
"newAccountName": "new_admin"
}In this example, a malicious user sends a POST request to the “/changeAccountName” endpoint, attempting to change the “admin” account name to “new_admin” without having proper administrative permissions. The attacker uses a valid user token for authentication, which does not have administrative permissions, thus exploiting the vulnerability.
