CVE-2025-7935
BaseFortify
Publication date: 2025-07-21
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 |
|---|---|---|
| fuyang_lipengjun | platform | to 2025-06-29 (inc) |
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-7935 is a critical SQL injection vulnerability in the fuyang_lipengjun platform, specifically in the SysLogController's /sys/log/list endpoint. The vulnerability occurs because the 'key' parameter from user input is not properly sanitized and is directly interpolated into SQL queries without using prepared statements. This allows an attacker to inject malicious SQL code remotely, potentially extracting sensitive data or gaining control over the server. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized disclosure of sensitive database information, manipulation of data, and potentially full compromise of the affected server. Attackers can remotely execute arbitrary SQL commands, which threatens the confidentiality, integrity, and availability of the system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the `/sys/log/list` endpoint with SQL injection payloads targeting the `key` parameter. A practical method is to use sqlmap with a crafted HTTP request to verify if SQL injection is possible. For example, you can capture a request to the endpoint and run: python sqlmap.py -r request.txt -p key --tamper=charencode,between --level 5 --flush-session -v 3 --current-db --batch This command tests the `key` parameter for SQL injection vulnerabilities by sending various payloads and analyzing the responses. Monitoring network traffic for suspicious requests to `/sys/log/list` with unusual or encoded parameters may also help detect exploitation attempts. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable `/sys/log/list` endpoint, for example by applying strict access controls or firewall rules to limit who can reach this endpoint. Since no patches or updated versions are available due to the rolling release model, consider replacing the affected component with an alternative product. Additionally, monitor logs for suspicious activity targeting the `key` parameter and disable or restrict the functionality if possible until a secure fix is implemented. [2]