CVE-2025-7888
BaseFortify
Publication date: 2025-07-20
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 |
|---|---|---|
| tduckcloud | tduck-platform | 5.1 |
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-7888 is a critical SQL injection vulnerability in TDuckCloud tduck-platform version 5.1. It occurs in the UserFormDataMapper function where the argument 'formKey' is improperly handled, allowing an attacker to inject malicious SQL code. This happens because the 'formKey' parameter is concatenated directly into an SQL query without proper sanitization or use of parameterized queries, enabling modification of the intended SQL commands. The vulnerability can be exploited remotely and affects the confidentiality, integrity, and availability of the system. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to execute arbitrary SQL commands on the affected system remotely. This can lead to unauthorized access to sensitive data, modification or deletion of data, and potential disruption of service, thereby compromising the confidentiality, integrity, and availability of your system. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the `/user/form/data/download/file` endpoint with specially crafted SQL injection payloads in the `formKey` parameter. Since the vulnerability requires authentication, you should perform authenticated requests. A common approach is to use tools like sqlmap or manual curl commands to inject SQL payloads and observe unexpected behavior or database errors. For example, using curl: `curl -X POST -d "formKey=' OR '1'='1" https://target-domain/user/form/data/download/file -b cookies.txt` where `cookies.txt` contains authenticated session cookies. Alternatively, use sqlmap targeting the parameter: `sqlmap -u "https://target-domain/user/form/data/download/file" --data="formKey=1" --cookie="SESSION=your_session_cookie" -p formKey --batch`. Monitoring logs for suspicious SQL errors or unusual database queries related to `formKey` can also help detect exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint `/user/form/data/download/file` to trusted users only, applying strict input validation and sanitization on the `formKey` parameter, and implementing parameterized queries or prepared statements to prevent SQL injection. Since no vendor patch or official fix is available, consider disabling or removing the affected functionality if possible. Monitoring for exploitation attempts and applying network-level protections such as Web Application Firewalls (WAF) with SQL injection detection rules can help reduce risk. Ultimately, replacing the affected component with an alternative product is recommended. [1, 2]