CVE-2025-11668
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-11668 is a SQL injection vulnerability in version 1.0 of the code-projects Automated Voting System, specifically in the /admin/update_user.php file. The vulnerability occurs because the 'password' parameter is not properly sanitized or validated, allowing attackers to inject malicious SQL code. This can be exploited remotely by authenticated users to manipulate the database, potentially leading to unauthorized access or modification of data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to perform unauthorized database access and manipulation, including data leakage, data tampering, full system compromise, and denial of service. It affects the confidentiality, integrity, and availability of the system, potentially disrupting business continuity and compromising sensitive information. [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 /admin/update_user.php endpoint for SQL injection on the password parameter. A proof-of-concept payload involves injecting SQL commands such as a time delay using MySQL's SLEEP function, e.g., password=222' AND (SELECT 6349 FROM (SELECT(SLEEP(5)))wRWu) AND 'jSao'='jSao. Additionally, the vulnerability was confirmed using the sqlmap tool with crafted HTTP POST requests targeting the vulnerable endpoint. Attackers may also locate vulnerable targets using Google dorking with the query inurl:admin/update_user.php. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product if possible, as no known countermeasures have been published. 2) Using prepared statements with parameter binding to separate SQL code from user input, preventing injection. 3) Implementing strict input validation and filtering to ensure inputs conform to expected formats. 4) Minimizing database user permissions by avoiding high-privilege accounts for routine operations. 5) Conducting regular security audits to detect and address vulnerabilities promptly. [1, 3]