CVE-2025-7557
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?
This vulnerability is a SQL injection flaw in the code-projects Voting System version 1.0, specifically in the file /admin/voters_row.php. It 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, enabling unauthorized manipulation of database queries such as retrieving, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
The vulnerability can impact you by compromising the confidentiality, integrity, and availability of the affected system. An attacker can remotely exploit this flaw without authentication to manipulate database contents, potentially accessing sensitive data, altering records, or disrupting system operations. This poses a significant security risk to any deployment using the vulnerable Voting System. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/voters_row.php endpoint for SQL injection using the 'id' parameter. A practical approach is to use the sqlmap tool with a crafted request file (e.g., poc.txt) containing a POST request to /admin/voters_row.php with the 'id' parameter. The suggested command is: python .\sqlmap.py -r .\poc.txt --dbs --batch. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:admin/voters_row.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected component with an alternative product if possible. If replacement is not feasible, implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. Also, apply strict input validation and filtering to ensure inputs conform to expected formats. No known countermeasures are documented, so these coding best practices are critical to mitigate the risk. [2, 3]