CVE-2025-11512VulnerabilityPublished 8 Oct 2025Updated 24 Feb 2026

CVE-2025-11512: code-projects Voting System · Cross Site Scripting

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:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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 8 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 Voting System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2025-11512, organizations should implement the following specific measures: 1) Apply input validation on the Firstname, Lastname, and Platform parameters to allow only expected characters and reject or sanitize any suspicious input. 2) Implement proper output encoding or escaping of user-supplied data before rendering it in the administrative interface to prevent script execution. 3) Restrict access to the /admin/voters_add.php endpoint to trusted networks and authenticated users only, using network segmentation and strong authentication mechanisms. 4) Monitor administrative logs and web traffic for unusual activities or attempts to inject scripts. 5) If available, apply official patches or updates from the vendor promptly. 6) Consider deploying Web Application Firewalls (WAFs) with rules to detect and block XSS payloads targeting the affected parameters. 7) Educate administrators about the risks of clicking on untrusted links and encourage the use of security-conscious browsing practices. 8) Conduct regular security assessments and code reviews to identify and remediate similar input validation issues proactively.

Description

A vulnerability was found in code-projects Voting System 1.0. Affected by this issue is some unknown functionality of the file /admin/voters_add.php. The manipulation of the argument Firstname/Lastname/Platform results in cross site scripting. The attack can be executed remotely. The exploit has been made public and could be used.

Impact

The primary impact of CVE-2025-11512 is on the confidentiality and integrity of administrative sessions within the code-projects Voting System. Successful exploitation allows attackers to execute arbitrary scripts in the administrator's browser, potentially leading to session hijacking, theft of sensitive credentials, or unauthorized changes to voter data. This can undermine the trustworthiness and accuracy of voting results, especially in environments where the system is used for official or organizational elections. Although availability is not directly affected, the indirect consequences of compromised administrative control could disrupt voting operations or lead to data manipulation. The vulnerability's remote exploitability without authentication increases the attack surface, particularly if administrative interfaces are exposed to untrusted networks. The public disclosure of exploit code raises the risk of opportunistic attacks, especially in organizations that have not implemented adequate input validation or security controls. Overall, the impact is significant for organizations relying on this system for critical voting functions, potentially leading to reputational damage, loss of stakeholder trust, and operational disruptions.

Summary

CVE-2025-11512 is a cross-site scripting (XSS) vulnerability identified in version 1.0 of the code-projects Voting System, specifically within the /admin/voters_add.php endpoint. The vulnerability stems from insufficient input validation and output encoding of the Firstname, Lastname, and Platform parameters, which are manipulated by attackers to inject malicious JavaScript code. This flaw allows remote attackers to execute arbitrary scripts in the context of an administrator's browser session without requiring authentication, although user interaction is necessary (e.g., the admin must visit a maliciously crafted URL). The vulnerability can lead to session hijacking, credential theft, or unauthorized administrative actions, compromising the confidentiality and integrity of the voting system's administrative functions. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, user interaction needed, and partial impact on integrity. Although no active exploits have been reported in the wild, the public availability of exploit code increases the likelihood of exploitation attempts. The vulnerability affects only version 1.0 of the product, and no official patches have been linked yet. Remediation involves implementing robust input validation, output encoding, and adopting secure coding practices to sanitize user inputs in the affected parameters. Organizations relying on this voting system for election or polling management should prioritize mitigation to prevent potential manipulation or disruption of voting data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:01 UTC

Technical details

References

Community reviews

Related threats