CVE-2025-12238VulnerabilityPublished 27 Oct 2025

CVE-2025-12238: code-projects Automated Voting System · SQL Injection

Affects code-projects Automated Voting SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Automated Voting System	Affected =1.0	Fixed in–

AI-suggested

1. Immediately restrict access to the /admin/user.php interface to trusted IP addresses or VPNs to reduce exposure. 2. Conduct a thorough code review of the affected function to identify and fix the SQL injection flaw by implementing parameterized queries or prepared statements. 3. Sanitize and validate all user inputs rigorously, especially the Username parameter, to prevent injection of malicious SQL code. 4. Monitor logs for suspicious SQL queries or unusual access patterns to detect potential exploitation attempts early. 5. If possible, isolate the voting system from public networks or place it behind a web application firewall (WAF) configured to detect and block SQL injection attempts. 6. Develop and deploy patches as soon as they become available from the vendor or consider upgrading to a newer, secure version if released. 7. Educate administrators on secure configuration and the importance of timely updates. 8. Implement regular security assessments and penetration testing focused on injection vulnerabilities. 9. Backup voting data frequently and securely to enable recovery in case of data tampering or loss.

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.

Impact

For European organizations, exploitation of this vulnerability could lead to unauthorized access and manipulation of voting data, compromising the integrity and confidentiality of election or polling results. This could erode public trust in electoral processes and potentially influence political outcomes. The availability of the voting system could also be affected if attackers execute disruptive SQL commands. Organizations relying on this system for internal or public voting may face reputational damage, legal consequences, and operational disruptions. Given the remote exploitability without authentication, attackers from anywhere could target these systems, increasing the threat landscape. The medium severity suggests that while the impact is significant, it may not lead to full system compromise or widespread outages, but targeted attacks on sensitive data are plausible. The lack of patches increases the urgency for organizations to implement compensating controls. The threat is particularly relevant for governmental bodies, political parties, and private organizations conducting critical votes in Europe.

Summary

CVE-2025-12238 identifies a SQL Injection vulnerability in the code-projects Automated Voting System version 1.0, located in an unspecified function within the /admin/user.php file. The vulnerability arises from improper sanitization or validation of the Username parameter, allowing an attacker to inject malicious SQL code remotely. The attack vector requires no user interaction and no prior authentication, making it accessible to remote unauthenticated attackers. The CVSS 4.0 vector indicates low complexity (AC:L), no privileges required (PR:L but no authentication needed), and no user interaction (UI:N). The impact on confidentiality, integrity, and availability is low to medium, as the attacker can potentially read or modify some data but not necessarily take full control or cause system-wide outages. No patches or fixes have been published yet, and no known exploits are actively used in the wild, though a public exploit has been released. The vulnerability could allow attackers to manipulate voting data, user information, or administrative records, undermining the trustworthiness of the voting system. The lack of secure coding practices such as parameterized queries or prepared statements is likely the root cause. Immediate remediation is critical to prevent exploitation, especially in environments where the voting system is used for official or sensitive polling.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 08:39 UTC

Technical details

References

Community reviews

Related threats