CVE-2025-13285VulnerabilityPublished 17 Nov 2025

CVE-2025-13285: itsourcecode Online Voting System · SQL Injection

Affects itsourcecode Online Voting SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 17 Nov 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
itsourcecode Online Voting System	Affected =1.0	Fixed in–

AI-suggested

Immediate mitigation steps include implementing strict input validation and sanitization for all user inputs, especially the Username parameter in /login.php. Employ parameterized queries or prepared statements to prevent SQL injection attacks. If possible, upgrade to a patched version of the itsourcecode Online Voting System once available. In the absence of official patches, consider deploying web application firewalls (WAFs) with rules to detect and block SQL injection attempts targeting this vulnerability. Conduct thorough code reviews and penetration testing focused on injection flaws. Restrict database permissions to the minimum necessary to limit the impact of any successful injection. Monitor logs for suspicious activities related to login attempts and SQL errors. Additionally, develop an incident response plan specific to election infrastructure to quickly address any exploitation attempts. Engage with the vendor for timely updates and advisories.

Description

CVE-2025-13285 is a medium severity SQL injection vulnerability affecting itsourcecode Online Voting System version 1.0. The flaw exists in the /login.php file where the Username parameter is improperly sanitized, allowing remote attackers to execute arbitrary SQL commands without authentication or user interaction. This vulnerability could lead to unauthorized data access, modification, or disruption of the voting system's availability. Although no known exploits are currently observed in the wild, a public exploit is available, increasing the risk of exploitation. European organizations using this voting system could face election manipulation, data breaches, and loss of public trust. Mitigation requires immediate input validation, parameterized queries, and patching or upgrading the affected software. Countries with higher adoption of this system or with critical election infrastructure relying on it are at greater risk. Given the ease of exploitation and potential impact on confidentiality, integrity, and availability, this vulnerability demands prompt attention.

Impact

For European organizations, especially electoral commissions and government bodies using the itsourcecode Online Voting System, this vulnerability poses significant risks. Exploitation could lead to unauthorized access to voter databases, manipulation of election results, and disruption of voting services, undermining democratic integrity and public trust. Data breaches could expose personally identifiable information of voters, violating GDPR and other privacy regulations, resulting in legal and financial repercussions. The availability impact could cause denial of service during critical election periods, affecting voter participation and confidence. The medium severity rating suggests moderate but tangible risks, particularly given the critical nature of voting systems. The public availability of an exploit increases the threat landscape, potentially attracting attackers ranging from hacktivists to nation-state actors interested in influencing elections or causing political instability within Europe.

Summary

CVE-2025-13285 identifies a SQL injection vulnerability in the itsourcecode Online Voting System version 1.0, specifically within the /login.php file's handling of the Username parameter. SQL injection occurs when user-supplied input is improperly sanitized and directly incorporated into SQL queries, allowing attackers to manipulate the database commands executed by the system. In this case, the vulnerability enables remote attackers to inject malicious SQL code without requiring authentication or user interaction, as indicated by the CVSS vector (AV:N/AC:L/AT:N/UI:N/PR:N). The vulnerability impacts confidentiality, integrity, and availability at a low level but is exploitable with low complexity. The presence of a publicly available exploit increases the likelihood of exploitation despite no current reports of active attacks. The affected system is an online voting platform, which is critical infrastructure for democratic processes. Exploitation could allow attackers to bypass authentication, retrieve sensitive voter data, alter vote counts, or disrupt the voting process entirely. The vulnerability's medium CVSS score (6.9) reflects these risks. No official patches have been published yet, increasing urgency for mitigation. The vulnerability was publicly disclosed on November 17, 2025, and is cataloged under CVE-2025-13285.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Nov 2025, 14:20 UTC

Technical details

References

Community reviews

Related threats