Overview
The CVE-2025-50341 is a high-risk, Boolean-based SQL injection vulnerability discovered in Axelor 5.2.4, an open-source business suite. This vulnerability can be exploited via the _domain parameter, allowing potential attackers to manipulate the SQL query logic and determine true/false conditions. The exploitation of this vulnerability could lead to significant data exposure or further system exploitation. Given the potentially severe impact, understanding this threat and applying appropriate mitigation measures are crucial for all users of Axelor 5.2.4.
Vulnerability Summary
CVE ID: CVE-2025-50341
Severity: Critical (9.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise and 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
Axelor | 5.2.4
How the Exploit Works
The CVE-2025-50341 vulnerability takes advantage of a flaw in the way the _domain parameter in Axelor 5.2.4 handles SQL queries. By manipulating the logic of these queries, an attacker can introduce additional conditions into the SQL statements. This leads to a Boolean-based SQL injection vulnerability, where the attacker can extract data by asking true or false questions and observing the application’s responses. If successfully exploited, this vulnerability can lead to unauthorized access to sensitive data or further system compromise.
Conceptual Example Code
Here’s a conceptual example of how the vulnerability might be exploited. This example is a sample HTTP request:
POST /axelor-crm HTTP/1.1
Host: target.example.com
Content-Type: application/json
{ "_domain": "1' OR '1'='1'; --" }In this example, `1′ OR ‘1’=’1′; –` is injected into the _domain parameter. This input manipulates the SQL query logic to always return true, potentially exposing sensitive data or providing unauthorized access to the system.
Mitigation
Users of Axelor 5.2.4 are strongly advised to apply the vendor’s patch to rectify this vulnerability. In situations where immediate patching is not possible, using Web Application Firewalls (WAF) or Intrusion Detection Systems (IDS) can serve as temporary mitigation. However, these do not provide a permanent solution and may not fully protect against all potential exploits of this vulnerability. It is crucial to apply the vendor patch as soon as feasibly possible to ensure maximum security.