CVE-2025-7581
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-7581 is a SQL injection vulnerability in the code-projects Voting System version 1.0, specifically in the file /admin/positions_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 SQL queries and database operations. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely exploit the system without authentication to manipulate the database. This can lead to unauthorized data modification, data disclosure, and potentially affect the confidentiality, integrity, and availability of the system. Attackers can perform unauthorized SQL commands, which may compromise the voting system's data and functionality. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable endpoint '/admin/positions_edit.php' and testing the 'id' parameter for SQL injection. One can use Google dorking with the query 'inurl:admin/positions_edit.php' to identify vulnerable targets. Additionally, tools like sqlmap can be used to automate detection and exploitation by sending crafted POST requests to the endpoint. For example, a command using sqlmap could be: sqlmap -u "http://target/admin/positions_edit.php" --data="id=9&description=test&max_vote=1&edit=" --risk=3 --level=5 --batch [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 not, implement prepared statements with parameter binding in the code to prevent SQL injection by separating SQL code from user input. Additionally, enforce strict input validation and filtering to ensure user inputs conform to expected formats. Avoid directly concatenating user input into SQL queries. Since no known countermeasures are documented, these coding best practices are critical to mitigate the vulnerability. [2, 3]