CVE-2025-7580VulnerabilityPublished 14 Jul 2025

CVE-2025-7580: code-projects Voting System · SQL Injection

Affects code-projects 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 33% 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 14 Jul 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 Voting System	Affected =1.0	Fixed in–

AI-suggested

Immediate mitigation steps include restricting external access to the /admin/positions_row.php endpoint by implementing network-level controls such as firewalls or VPN requirements. Organizations should conduct a thorough code review and apply input validation and parameterized queries or prepared statements to the 'ID' parameter to prevent SQL injection. If possible, upgrade to a newer, patched version of the Voting System once available. In the interim, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting this endpoint. Regularly monitor logs for suspicious database queries or unusual access patterns. Segmentation of the voting system backend from other critical infrastructure reduces lateral movement risk. Additionally, implement strict database user permissions limiting the impact of any successful injection. Finally, organizations should prepare incident response plans specific to election systems to quickly address any compromise.

Description

A vulnerability classified as critical was found in code-projects Voting System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/positions_row.php. The manipulation of the argument ID leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the code-projects Voting System version 1.0, this vulnerability could have severe consequences. The integrity and confidentiality of voting data could be compromised, leading to manipulation or disclosure of sensitive electoral information. This undermines democratic processes and public trust in election outcomes. Additionally, attackers could disrupt availability by deleting or corrupting voting records, causing operational outages during critical election periods. The medium CVSS score suggests limited impact scope or partial mitigations, but the critical nature of voting systems amplifies the real-world impact beyond typical business applications. Organizations involved in local or regional elections, political parties, or governmental bodies using this software are at risk. The lack of authentication requirement and remote exploitability increases the attack surface, especially if the system is exposed to the internet or poorly segmented networks. Furthermore, the absence of known exploits currently does not preclude future active exploitation, especially as proof-of-concept code becomes available publicly.

Summary

CVE-2025-7580 is a SQL Injection vulnerability identified in version 1.0 of the code-projects Voting System, specifically within the /admin/positions_row.php file. The vulnerability arises from improper sanitization or validation of the 'ID' parameter, which can be manipulated by an attacker to inject malicious SQL code. This flaw allows an unauthenticated remote attacker to execute arbitrary SQL queries on the backend database. The vulnerability does not require user interaction and can be exploited over the network without authentication, increasing its risk profile. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L) which suggests some limited privileges might be needed but the description states remote exploitation is possible without authentication, no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). The vulnerability has been publicly disclosed but there are no known exploits in the wild at this time. The absence of patches or mitigation links implies that the vendor has not yet released an official fix. SQL Injection vulnerabilities typically allow attackers to read, modify, or delete data, and potentially escalate to full system compromise depending on database permissions and system architecture. Given the critical classification in the description but a medium CVSS score, this discrepancy may be due to limited impact or exploitation complexity nuances. However, the ability to remotely execute SQL commands on a voting system backend poses significant risks to data integrity and trustworthiness of election-related data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2025, 07:01 UTC

Technical details

References

Community reviews

Related threats