CVE-2025-6100
BaseFortify
Publication date: 2025-06-16
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
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-6100 is a critical SQL injection vulnerability in version 1.0 of the realguoshuai open-video-cms system. It affects the /v1/video/list endpoint, where the 'sort' parameter is improperly handled and not properly sanitized. This allows an attacker to inject malicious SQL code remotely, potentially gaining unauthorized access to sensitive data stored in the system's database. [1, 2]
How can this vulnerability impact me? :
This vulnerability can compromise the confidentiality, integrity, and availability of the affected system. An attacker exploiting this SQL injection flaw can access sensitive information, manipulate or delete data, and disrupt the normal operation of the system. Since the exploit is publicly available and the vulnerability is remotely exploitable without authentication, it poses a significant security risk. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring requests to the endpoint `/v1/video/list` for suspicious or malformed `sort` parameter values that may indicate SQL injection attempts. Since a proof-of-concept exploit is publicly available, you can test the endpoint by sending crafted HTTP requests with SQL injection payloads in the `sort` parameter and observe the responses for errors or unexpected behavior. For example, using curl: `curl -v 'http://<target>/v1/video/list?sort=1'` and then testing with payloads like `sort=1' OR '1'='1` to see if the response indicates SQL injection vulnerability. Additionally, network intrusion detection systems (NIDS) or web application firewalls (WAF) can be configured to detect SQL injection patterns targeting this endpoint. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
No known mitigations or countermeasures are currently available for this vulnerability, and the vendor has not responded to disclosure attempts. Immediate steps include restricting access to the vulnerable endpoint `/v1/video/list` if possible, such as by implementing network-level controls or web application firewall rules to block or monitor suspicious input in the `sort` parameter. Consider replacing the affected product with an alternative solution that is not vulnerable. Monitoring for exploitation attempts and applying strict input validation or sanitization if you have the ability to modify the source code are also recommended. [2]