CVE-2025-50341
BaseFortify
Publication date: 2025-08-04
Last updated on: 2025-08-05
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| axelor | axelor | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-50341 is a Boolean-based SQL injection vulnerability in Axelor version 5.2.4 affecting the "_domain" parameter. An attacker can inject Boolean conditions into this parameter to manipulate the SQL query logic, allowing them to infer true or false responses from the server. This can lead to the attacker extracting or dumping database contents by observing differences in server responses. [1]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to access sensitive data stored in the database by exploiting the SQL injection flaw. By manipulating the "_domain" parameter, the attacker can extract confidential information, potentially leading to data exposure, unauthorized data access, and further exploitation of the system. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by intercepting requests containing the "_domain" parameter and injecting Boolean payloads such as '1=1' or '1=2' into it. By observing differences in server responses to these injections, you can infer the presence of the Boolean-based SQL injection. Specific commands are not provided, but the process involves using a proxy or interception tool to modify requests and analyze responses. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include using parameterized queries or prepared statements to separate SQL logic from user input, employing modern ORM libraries (like Sequelize, Prisma, TypeORM) to enforce safe query practices, and rigorously validating and sanitizing inputs. Enforce strict input formats (e.g., numeric IDs only containing digits), reject or sanitize invalid inputs, and prefer allow-lists over block-lists for input validation. [1]