CVE-2026-14648
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 · uneditedA security vulnerability has been detected in code-projects Online Voting System up to 0.x/1.0. This issue affects the function test_input of the file /authentication.php of the component Login. Such manipulation of the argument adminUserName/adminPassword leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used.
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 · high confidenceSQL injection vulnerability in the login function (test_input) of /authentication.php in code-projects Online Voting System up to version 1.0. The adminUserName and adminPassword parameters are not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the authentication.php fileSearch the web server document root for the file /authentication.php or look in the application directory for a file named authentication.phpAffected if The file does not exist, the system is not the Online Voting System or a different authentication mechanism is used
-
Identify the installed versionCheck for a version file, footer, or config file in the application that displays the version number, or compare the file timestamps and structure to the 1.0 releaseAffected if The installed version is 1.0 or cannot be determined but appears to be the base release
-
Examine the test_input functionOpen authentication.php and locate the test_input function definition to see if it performs input sanitization, escaping, or uses prepared statementsAffected if The test_input function does not use prepared statements, mysqli_real_escape_string, or other proper sanitization methods
-
Check SQL query construction for login parametersFind the SQL query that uses adminUserName and adminPassword parameters and verify if they are passed directly to the query or bound as parametersAffected if The parameters are concatenated directly into the SQL query string without parameter binding
-
Verify the application is accessibleConfirm the web server is running and the Online Voting System login page at /authentication.php or the login page that calls it is accessible over the networkAffected if The login function is accessible remotely and accepts user input for adminUserName and adminPassword
The environment is affected if the Online Voting System version 1.0 is installed, the authentication.php file contains the vulnerable test_input function, and the adminUserName/adminPassword parameters are used in unsanitized SQL queries.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with prepared statements/parameterized queries in the test_input function and apply proper input validation and escaping for all user-supplied authentication parameters.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14648 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14648 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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