CVE-2025-8203
BaseFortify
Publication date: 2025-07-26
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 |
|---|---|---|
| jingmen_zeyou | large_file_upload_control | to 6.3 (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-8203 is a critical SQL injection vulnerability in Jingmen Zeyou Large File Upload Control up to version 6.3, specifically in the /index.jsp file. The vulnerability arises from improper handling of the "id" parameter, which allows an attacker to inject malicious SQL code remotely without authentication. This can lead to unauthorized manipulation of the database, data leakage, or potentially gaining control over the server. The vulnerability is publicly disclosed with proof-of-concept exploits available. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely exploit the SQL injection flaw to manipulate your database, potentially leading to unauthorized data access, data leakage, modification or deletion of data, and even full server compromise. Since it can be exploited without authentication and has publicly available proof-of-concept exploits, it poses a significant security risk to 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?
The vulnerability can be detected by testing the 'id' parameter in the /index.jsp file for SQL injection. A proof-of-concept detection method uses the sqlmap tool with a crafted HTTP request. For example, using the command: sqlmap -r 1.txt --dbs --batch --random-agent -p id --force-ssl --level 4, where '1.txt' contains the HTTP request to the vulnerable URL. This command targets the 'id' parameter for injection, forces SSL, uses a random user agent, and performs a thorough scan to confirm the SQL injection vulnerability. [3]
What immediate steps should I take to mitigate this vulnerability?
No vendor response or official mitigation measures are available. Immediate steps include replacing the affected product with an alternative solution, restricting access to the vulnerable endpoint if possible, and monitoring for exploitation attempts. Since the vulnerability is remotely exploitable without authentication and a public proof-of-concept exists, it is critical to limit exposure until a patch or fix is provided. [2, 3]