CVE-2025-10399
BaseFortify
Publication date: 2025-09-14
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| korzh | easyquery | 7.4.0 |
| korzh | easyquery | * |
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. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-10399 is a SQL Injection vulnerability in Korzh EasyQuery versions up to 7.4.0. It occurs because the software fails to properly sanitize or escape numerical input values in API requests, specifically in the /api/easyquery/models/nwind/fetch endpoint of the Query Builder UI component. This allows an attacker to inject malicious SQL commands remotely, bypassing input validation done only in the UI but not at the backend. As a result, attackers can execute arbitrary SQL queries on the underlying database, potentially accessing or manipulating sensitive data. [1, 2]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to remotely execute arbitrary SQL commands on your database through the vulnerable EasyQuery API. This can lead to unauthorized access to sensitive data, data modification, or deletion, compromising the confidentiality, integrity, and availability of your system. The exploit bypasses any restrictions imposed by EasyQuery's data model, granting full access to the data source. Since a public proof-of-concept exploit is available, the risk of exploitation is high. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted JSON requests to the vulnerable endpoint `/api/easyquery/models/nwind/fetch` that include SQL injection payloads in numerical value fields. For example, sending a request with a payload like "val":"1) union select @@version --" (for MSSQL) or "val":"1) union select 'v' || sqlite_version() --" (for SQLite) can confirm exploitation if the response contains database version information. Detection involves monitoring for such suspicious requests or responses revealing database details. Specific commands would involve using tools like curl or HTTP clients to send these crafted JSON payloads to the API endpoint and analyzing the responses for SQL injection success indicators. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or blocking access to the vulnerable API endpoint `/api/easyquery/models/nwind/fetch` to prevent remote exploitation. Since no patches or fixes are currently available, consider replacing the affected Korzh EasyQuery product with an alternative solution. Additionally, implement network-level protections such as web application firewalls (WAFs) to detect and block SQL injection attempts targeting this endpoint. [2]