dbcve.org
InjectionWeakness · CWE-74

CVE-2026-14649

HIGH · 7.3 CVSS v3.1 Published 2026-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in code-projects Online Voting System 1.0 where the test_input function in /saveVote.php fails to properly sanitize user input in the voterName, voterEmail, voterID, and selectedCandidate parameters, allowing remote attackers to inject malicious SQL queries.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) for all database operations in saveVote.php and implement proper input validation in the test_input function to neutralize SQL injection payloads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Online Voting System installation
    Locate the web application root directory and identify if the code-projects Online Voting System version 1.0 is deployed. Check for typical installation paths such as /var/www/html/voting, /var/www/voting-system, or C:\xampp\htdocs\voting. Look for application files including index.php, saveVote.php, and configuration files.
    Affected if The application is code-projects Online Voting System version 1.0
  2. Confirm saveVote.php exists
    Locate the saveVote.php file within the web application directory structure. This file handles vote submission and contains the vulnerable test_input function.
    Affected if The file saveVote.php exists in the application
  3. Inspect test_input function implementation
    Open saveVote.php and locate the test_input function. Examine how it processes the voterName, voterEmail, voterID, and selectedCandidate parameters. Check if it uses basic string manipulation (such as trim, stripslashes, or htmlspecialchars) without proper SQL escaping or uses a proper sanitization library.
    Affected if The test_input function relies only on basic string functions and does not use prepared statements or proper SQL escaping methods
  4. Check SQL query construction in saveVote.php
    Examine the database query code in saveVote.php where voterName, voterEmail, voterID, and selectedCandidate are used. Look for queries constructed by string concatenation or string interpolation (e.g., "SELECT * FROM voters WHERE name='" . $voterName . "'") rather than parameterized queries using prepare() and bindParam().
    Affected if SQL queries are built using string concatenation with user input rather than prepared statements with bound parameters
  5. Test parameter susceptibility (optional)
    If authorized to perform penetration testing, submit a vote with SQL injection payloads in the voterName, voterEmail, voterID, or selectedCandidate fields (e.g., voterName: "' OR '1'='1"). Observe if the application returns unexpected database errors or behaves differently based on the payload.
    Affected if SQL injection payloads produce unexpected application behavior or database errors indicating successful injection

The environment is affected if running Online Voting System 1.0 with the saveVote.php file containing dynamically constructed SQL queries that rely on the test_input function for input handling instead of parameterized queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries (prepared statements) for all database operations in saveVote.php and implement proper input validation in the test_input function to neutralize SQL injection payloads.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14649 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14649 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data