CVE-2025-7580
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-7580 is a critical SQL injection vulnerability in the code-projects Voting System 1.0, specifically in the file /admin/positions_row.php. The vulnerability occurs because the application directly inserts user-supplied input from the 'id' parameter into an SQL query without proper sanitization or parameterization. This allows an attacker to inject malicious SQL code remotely, potentially compromising the database by manipulating SQL queries. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely execute arbitrary SQL commands on your database. This can lead to unauthorized access, modification, or deletion of data, compromising the confidentiality, integrity, and availability of your system. Attackers can exploit this flaw to extract sensitive information, alter data, or disrupt system operations. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted POST requests to the vulnerable endpoint /admin/positions_row.php with manipulated 'id' parameters to test for SQL injection. One practical method is to use the sqlmap tool with a prepared HTTP request file (e.g., poc.txt) containing the vulnerable request. The command to enumerate databases is: sqlmap.py -r poc.txt --dbs --batch. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:admin/positions_row.php. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, ensuring that the 'id' parameter is treated strictly as data. Also, apply strict input validation and filtering to ensure the 'id' parameter conforms to expected formats before processing. If possible, replace the affected component with an alternative product. These measures prevent execution of injected SQL commands and mitigate the SQL injection vulnerability. [1, 2]