CVE-2025-11667
BaseFortify
Publication date: 2025-10-13
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 | automated_voting_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-11667 is a SQL injection vulnerability in version 1.0 of the code-projects Automated Voting System, specifically in the file /admin/add_candidate_modal.php. The vulnerability occurs because the application improperly handles the 'firstname' parameter, allowing an attacker to inject malicious SQL code remotely without authentication. This happens due to lack of proper input sanitization and validation, enabling attackers to manipulate SQL queries directly, potentially compromising the database and system security. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely execute SQL injection attacks that compromise the confidentiality, integrity, and availability of your system. Exploitation can lead to unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption. Since a public proof-of-concept exploit exists, the risk of exploitation is high, which can severely affect system security and business continuity. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'firstname' parameter in the /admin/add_candidate_modal.php file for SQL injection. One effective method is to use the sqlmap tool to perform an automated SQL injection test targeting this parameter with a multipart/form-data POST request. For example, a command like: sqlmap -u "http://target/admin/add_candidate_modal.php" --data="firstname=anything" --method=POST --risk=3 --level=5 --technique=BEUSTQ --batch can be used to detect the vulnerability. Additionally, manual testing by injecting payloads such as 'SLEEP(5)' in the firstname parameter and observing response delays can confirm time-based blind SQL injection. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replace or update the affected component or product if a fixed version is available. 2) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 3) Apply strict input validation and filtering on the 'firstname' parameter to ensure only expected data is accepted. 4) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 5) Conduct regular security audits to identify and remediate vulnerabilities promptly. Since no known mitigations are currently available, replacing the vulnerable component is strongly recommended. [1, 3]