CVE-2025-14012
BaseFortify
Publication date: 2025-12-04
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 |
|---|---|---|
| jizhicms | jizhicms | to 2.5.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in JIZHICMS up to version 2.5.5, specifically in the Batch Delete Comments component's deleteAll/findAll/delete functions within the /index.php/admins/Comment/deleteAll.html file. It allows an attacker to perform SQL injection by manipulating these functions remotely, potentially compromising the database.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access and manipulation of the database through SQL injection. This can result in data leakage, data modification, or deletion, impacting the confidentiality, integrity, and availability of the affected system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for the vulnerable endpoint /index.php/admins/Comment/deleteAll.html on your system or network. Using Google dorking with the query inurl:index.php/admins/Comment/deleteAll.html can help identify vulnerable targets. Additionally, testing the deleteAll/findAll/delete functions for SQL injection by sending crafted payloads to the data parameter in the deleteAll.html endpoint can reveal exploitation attempts. Specific commands might include using curl or similar tools to send SQL injection test payloads to the endpoint, for example: curl -X POST 'http://target/index.php/admins/Comment/deleteAll.html' --data 'data=1 OR 1=1' to check for SQL injection responses. [1]
What immediate steps should I take to mitigate this vulnerability?
No known mitigations or patches have been published by the vendor, and the vendor did not respond to disclosure attempts. Immediate steps include replacing the affected component or the entire JIZHICMS system with an alternative product that is not vulnerable. Additionally, restricting access to the vulnerable endpoint to trusted users only and monitoring for suspicious activity can help reduce risk until a fix or patch is available. [1]