CVE-2025-7556
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-7556 is a SQL injection vulnerability in the code-projects Voting System version 1.0, specifically in the file /admin/voters_edit.php. The vulnerability occurs because the application directly uses the 'id' parameter from user input in SQL queries without proper sanitization or validation. This allows an attacker to inject malicious SQL code through the 'id' parameter, enabling unauthorized manipulation of the database remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to perform unauthorized database operations such as reading, modifying, or deleting data. It compromises the confidentiality, integrity, and availability of the system. Since the exploit can be launched remotely without authentication and proof-of-concept exploits are publicly available, it poses a significant security risk to affected systems. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by sending crafted POST requests to the vulnerable endpoint /admin/voters_edit.php with manipulated 'id' parameters. Tools like sqlmap can be used to automate detection by targeting this endpoint. For example, using sqlmap with a POST request containing the 'id' parameter can help identify the vulnerability. Additionally, searching for the vulnerable URL using Google dorking with the query "inurl:admin/voters_edit.php" can help identify exposed instances. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no known mitigations or countermeasures have been documented. Additionally, if possible, apply code fixes by using prepared statements with parameter binding to prevent SQL injection, and implement strict input validation and filtering to ensure user inputs conform to expected formats. [2, 3]