CVE-2025-12238
Unknown Unknown - Not Provided

BaseFortify

Publication date: 2025-10-27

Last updated on: 2026-04-29

Assigner: VulDB

Description
A security flaw has been discovered in code-projects Automated Voting System 1.0. The affected element is an unknown function of the file /admin/user.php. Performing manipulation of the argument Username results in sql injection. The attack is possible to be carried out remotely. The exploit has been released to the public and may be exploited.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2025-10-27
Last Modified
2026-04-29
Generated
2026-07-06
AI Q&A
2025-10-27
EPSS Evaluated
2026-07-05
NVD
CVE-2025-12238
EUVD
EUVD-2025-36099

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
fabian automated_voting_system 1.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2025-12238 is a SQL injection vulnerability in the Automated Voting System version 1.0, specifically in the /admin/user.php file. The vulnerability occurs because the 'username' parameter is not properly validated or sanitized, allowing an attacker to inject malicious SQL code remotely. This can lead to unauthorized database queries and manipulation. [1, 2, 4]

Impact Analysis

This vulnerability can allow attackers to gain unauthorized access to the database, leak sensitive data, manipulate or delete data, compromise the entire system, and disrupt services. Since the exploit is publicly available and can be executed remotely without authentication, the risk of exploitation is high. [2, 4]

Detection Guidance

This vulnerability can be detected by testing the /admin/user.php endpoint for SQL injection in the 'username' parameter. One approach is to use automated tools like sqlmap to test for SQL injection by sending crafted payloads to the 'username' field in a POST request. For example, using sqlmap with the vulnerable URL and specifying the 'username' parameter can confirm the injection point. Additionally, time-based blind SQL injection can be tested by injecting payloads that cause delays (e.g., sleep commands) and observing delayed server responses. Google dorking with the query 'inurl:admin/user.php' can help identify vulnerable targets on your network or externally. [2, 4]

Mitigation Strategies

Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Apply strict input validation and filtering on the 'username' parameter to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, replace the affected software with an alternative product as no known mitigations are documented. These steps help protect system security and data integrity. [2, 4]

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-12238. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart