HIGH 7.3

CVE-2026-14649: SQL Injection in code-projects Online Voting System 1.0

A SQL injection vulnerability exists in code-projects Online Voting System version 1.0. The vulnerability affects the voting submission functionality, specifically the `/saveVote.php` file's `test_input` function. An attacker can manipulate voter-related fields (voterName, voterEmail, voterID, or selectedCandidate) to inject malicious SQL commands. Because the vulnerability requires no authentication and can be triggered remotely over the network, an attacker can exploit it without prior system access or user interaction.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.3 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Weaknesses (CWE)
CWE-74, CWE-89
Affected products
0 configuration(s)
Published / Modified
2026-07-04 / 2026-07-07

NVD description (verbatim)

A vulnerability was detected in code-projects Online Voting System 1.0. Impacted is the function test_input of the file /saveVote.php. Performing a manipulation of the argument voterName/voterEmail/voterID/selectedCandidate results in sql injection. The attack can be initiated remotely.

7 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-14649 is a network-accessible SQL injection flaw in the `test_input` function within `/saveVote.php` of code-projects Online Voting System 1.0. The vulnerability arises from insufficient input validation on four parameters: voterName, voterEmail, voterID, and selectedCandidate. Attackers can craft malformed input to break out of SQL query context and execute arbitrary database commands. The flaw is classified under CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component) and CWE-89 (SQL Injection), indicating both the root cause and the downstream impact.

Business impact

A successful exploit could allow attackers to read, modify, or delete voting records and other sensitive database contents. This poses a direct threat to the integrity of elections or polls conducted using this system. Additionally, attackers may extract personally identifiable information stored in the database, leading to privacy breaches and regulatory exposure. The confidentiality, integrity, and availability of the voting platform are all at risk.

Affected systems

The vulnerability specifically affects code-projects Online Voting System version 1.0. Organizations or individuals running this version are immediately vulnerable. The system is accessible remotely via HTTP/HTTPS, meaning any internet-connected instance is exposed to potential exploitation attempts.

Exploitability

This vulnerability has a CVSS v3.1 score of 7.3 (HIGH severity) with a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. The high exploitability is due to the attack being remotely exploitable without authentication (PR:N) or user interaction (UI:N), and with low attack complexity (AC:L). The lack of CISA KEV listing does not diminish the practical exploitability—it reflects the current state of public exploitation tracking rather than the inherent ease of weaponization.

Remediation

Immediate action is required: upgrade to a patched version of code-projects Online Voting System if available from the vendor. If no patch exists, implement strict input validation and parameterized SQL queries in the affected `/saveVote.php` file's `test_input` function for all four vulnerable parameters. Additionally, apply Web Application Firewall (WAF) rules to detect and block SQL injection patterns in voting-related requests, and conduct a forensic review of database logs to determine if the vulnerability has been exploited.

Patch guidance

Check the code-projects or vendor advisory for available patches addressing CVE-2026-14649. Apply patches to all instances of Online Voting System 1.0 in your environment. Verify that input sanitization and parameterized queries are in place for voterName, voterEmail, voterID, and selectedCandidate parameters. If the vendor has not released a patch, prioritize migrating to an alternative, actively maintained voting system solution.

Detection guidance

Monitor `/saveVote.php` access logs for suspicious SQL syntax patterns in POST parameters (e.g., single quotes, UNION keywords, comment sequences). Deploy network-based detection for SQL injection payloads targeting the voting submission endpoint. Use database activity monitoring to identify unusual query patterns or unauthorized data access attempts. Review application logs for errors that may indicate failed SQL injection attempts. Consider deploying a WAF with SQL injection signatures configured specifically for this voting application.

Why prioritize this

Despite not being listed on the CISA KEV catalog, this vulnerability demands immediate prioritization because it affects a critical voting system with no authentication barriers and direct remote access. The HIGH CVSS score reflects multiple impact areas (confidentiality, integrity, availability), and the lack of user interaction requirements means exploitation can occur at scale automatically. Any organization running this system should treat patching or decommissioning as urgent.

Risk score, explained

The CVSS 7.3 (HIGH) score reflects the convergence of high exploitability (network-accessible, no authentication, no user interaction) and moderate-to-broad impact across confidentiality, integrity, and availability. The low attack complexity indicates that standard SQL injection techniques will likely succeed. While the scope is unchanged (impact within the voting system itself), the combination of ease of exploitation and the sensitive nature of the affected system (voting data) justifies the HIGH rating.

Frequently asked questions

Can this vulnerability be exploited without internet access?

No. The vulnerability requires network access to the `/saveVote.php` endpoint. However, any instance of the Online Voting System accessible over a network—including internal networks—is potentially vulnerable if the attacker has network connectivity.

Does patching the database alone fix this vulnerability?

No. Patching the database management system will not address the root cause, which is insufficient input validation in the application code. The application layer must be fixed by implementing proper input sanitization and parameterized SQL queries, or by upgrading to a patched version of the voting system.

Is there public exploit code available for this vulnerability?

As of the current knowledge cutoff, CISA has not listed this vulnerability in its KEV catalog, suggesting public exploitation activity has not yet been widely reported. However, this does not mean exploits do not exist; SQL injection is a well-understood attack class, and this vulnerability's straightforward nature makes it easy to exploit independently.

What immediate steps should a voting system administrator take?

First, verify whether your instance is affected by checking your Online Voting System version. If running version 1.0, immediately take the system offline or restrict network access until patches are applied. Check the code-projects vendor for available patches. Simultaneously, review database logs for any signs of exploitation. If no patches are available and the system is critical, evaluate migration to an alternative solution.

This analysis is provided for informational purposes based on publicly available vulnerability data. SEC.co does not guarantee the completeness or accuracy of vendor-specific patch information; verify all remediation steps against official vendor advisories. Organizations should conduct their own risk assessment based on their specific environment, deployment, and business context. This summary does not constitute legal or compliance advice. Exploitation attempts may be illegal in certain jurisdictions; consult your legal team before conducting any security testing. Source: NVD (public-domain), retrieved 2026-08-13. Analysis generated by SEC.co (claude-haiku-4-5).