CVE-2025-7555
BaseFortify
Publication date: 2025-07-14
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 |
|---|---|---|
| fabian | voting_system | 1.0 |
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-7555 is a critical SQL injection vulnerability in code-projects Voting System 1.0, specifically in the /admin/voters_add.php file. The vulnerability occurs because user inputs, such as firstname and lastname, are directly concatenated into an SQL query without proper sanitization or parameterization. This allows an attacker to inject malicious SQL code remotely, potentially manipulating the database queries executed by the system. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely execute arbitrary SQL commands on the database. This can lead to unauthorized access to sensitive data, modification or deletion of data, and potentially compromise the confidentiality, integrity, and availability of the voting system. Exploitation can result in data breaches or disruption of service. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by scanning for the presence of the vulnerable endpoint /admin/voters_add.php, for example using Google dorking with the query 'inurl:admin/voters_add.php'. Additionally, tools like sqlmap can be used to test for SQL injection by sending crafted HTTP POST requests to /admin/voters_add.php with manipulated firstname or lastname parameters to confirm the vulnerability. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected product with an alternative, as no known mitigations are documented. Additionally, if possible, modify the code to use prepared statements with parameter binding to prevent SQL injection. Implement strict input validation and filtering on the firstname and lastname parameters to ensure they conform to expected formats and do not contain malicious SQL code. [1, 2]