CVE-2025-7558
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-7558 is a SQL injection vulnerability in the code-projects Voting System version 1.0, specifically in the /admin/positions_add.php file. The vulnerability occurs because the application directly uses user-supplied input from the 'description' parameter in SQL queries without proper sanitization or validation. This allows an attacker to inject malicious SQL code, manipulating the database queries to execute unauthorized operations. [1, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely execute unauthorized SQL commands on your database without authentication. 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 manipulate database contents, potentially causing data breaches or service disruptions. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying the presence of the vulnerable endpoint '/admin/positions_add.php' in the code-projects Voting System 1.0. One method is using Google dorking with the query 'inurl:admin/positions_add.php' to find potentially vulnerable targets. Additionally, tools like sqlmap can be used to test for SQL injection by sending crafted POST requests to the endpoint with parameters such as 'description' and 'max_vote'. For example, using sqlmap to test injection on the 'description' parameter can help detect the vulnerability. [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, apply strict input validation and filtering on the 'description' and 'max_vote' parameters to ensure they conform to expected formats. Implement prepared statements with parameter binding in the code to separate SQL commands from user input, preventing SQL injection. These steps will help prevent attackers from injecting malicious SQL code through user inputs. [2, 3]