Description

Unauthenticated PHP Object Injection in AI ANN <= 1.29.0 versions.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "9.8",
  "pubDate": "2026-08-06T15:17:19.683Z",
  "pubdate": "2026-08-06T15:17:19.683Z",
  "executiveSummary": "An unauthenticated PHP Object Injection vulnerability has been identified in AI ANN versions <= 1.29.0. This security flaw enables remote, unauthenticated threat actors to supply maliciously crafted serialized data to the vulnerable application logic, bypassing standard authentication barriers entirely.\nThe primary impact of this vulnerability is the potential for Remote Code Execution (RCE), arbitrary file manipulation, or sensitive data disclosure, depending on the presence of suitable gadget chains within the application scope or its dependent libraries. The risk implications are severe, as successful exploitation grants attackers the ability to compromise the underlying host system, execute arbitrary system commands with the privileges of the web server, and pivot deeper into the network.\nExploitation requirements are minimal regarding authentication, as the attack vector is unauthenticated over the network. However, successful payload execution typically relies on the availability of exploitable magic methods and classes within the PHP object instantiation lifecycle. Organizations utilizing affected versions face critical risk exposure and are urged to implement immediate remediation strategies.",
  "technicalDetails": "The vulnerability resides in the application's handling of user-supplied input that is insecurely passed into PHP's native unserialize() function or an equivalent insecure deserialization mechanism within AI ANN <= 1.29.0.\nRoot Cause: The root cause of the vulnerability is the lack of proper input validation and sanitization prior to the deserialization of untrusted data. When the application reconstructs PHP objects from serialized strings provided by unauthenticated remote users without verifying the integrity or origin of the data, it exposes the execution flow to manipulation.\nAttack Flow and Exploitation Method: 1. The attacker identifies an entry point accepting serialized data over the network without requiring authentication. 2. The attacker crafts a malicious payload containing a serialized object structure designed to leverage existing application or library classes containing magic methods such as __wakeup() or __destruct(). 3. The attacker transmits the crafted payload via HTTP requests to the vulnerable component. 4. The application processes the input and invokes the unserialize() function on the untrusted data. 5. PHP instantiates the specified class and automatically triggers the associated magic methods, executing the attacker-controlled logic. 6. The malicious gadget chain executes, leading to downstream impacts such as arbitrary file read/write or remote code execution.\nVulnerable Component: The serialization and deserialization handling routines within AI ANN <= 1.29.0.\nAuthentication and Privileges: No authentication is required to initiate the attack vector, and zero administrative or low-privileged user privileges are necessary.\nNetwork Exposure: The vulnerability is exploitable remotely over the network via HTTP/HTTPS protocols if the vulnerable endpoint is accessible to the attacker.\nPayload Behavior and Post-Exploitation Impact: The payload utilizes available gadget chains to manipulate application state or execute system commands. Post-exploitation impact includes full system compromise, data exfiltration, lateral movement, and establishment of persistent unauthorized access."
}