Overview
The vulnerability, identified as CVE-2025-49852, affects ControlID iDSecure On-premises versions 4.7.48.0 and prior. It’s a server-side request forgery vulnerability that enables an unauthenticated attacker to retrieve information from other servers. This vulnerability is of particular concern due to the potential for system compromise and data leakage.
Vulnerability Summary
CVE ID: CVE-2025-49852
Severity: High (7.5 CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise and potential 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
ControlID iDSecure On-premises | 4.7.48.0 and prior
How the Exploit Works
The exploit takes advantage of a server-side request forgery vulnerability in ControlID iDSecure. An unauthenticated attacker can send a crafted request to the vulnerable server. This request tricks the server into making a network connection back to itself or to other systems, allowing the attacker to retrieve sensitive information, potentially leading to system compromise or data leakage.
Conceptual Example Code
The following is a conceptual example of how the vulnerability might be exploited. In this case, the malicious payload tricks the server into making a request back to itself or other servers.
POST /vulnerable/endpoint HTTP/1.1
Host: target.example.com
Content-Type: application/json
{
"url": "http://localhost/admin"
}In this example, the malicious payload is a JSON object containing a URL that the server will request. The URL points to a local or remote server from which the attacker wants to retrieve information.