Is there a public PoC exploit available for CVE-2026-14648?

Yes, a public proof-of-concept exploit is available for CVE-2026-14648. Prioritise patching immediately. EPSS: 0.3%.

Online Voting System CVE-2026-14648

Q: What is the CVSS score of CVE-2026-14648?

CVE-2026-14648 has a CVSS 4.0 base score of 5.5 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-41692 MEDIUM

SQL Injection (CWE-89)

2026-07-04 VulDB

PHP SQLi Online Voting System Code Projects

5.5

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

5.5 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

9.4 CRITICAL

Unauthenticated network login endpoint yields full DB read (C:H) and auth bypass/write (I:H); minor availability risk from query manipulation warrants A:L.

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

CVSS changed

Jul 04, 2026 - 20:22 NVD

6.9 (MEDIUM) 5.5 (MEDIUM)

Analysis Generated

Jul 04, 2026 - 20:21 vuln.today

DescriptionCVE.org

A 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.

AnalysisAI

Unauthenticated SQL injection in code-projects Online Voting System 0.x-1.0 exposes the admin login endpoint to full authentication bypass and database extraction. The vulnerability resides in the test_input function within /authentication.php, where the adminUserName and adminPassword parameters are passed unsanitized into SQL queries, enabling classic injection attacks against the login form. A public proof-of-concept exploit has been published on GitHub; no vendor patch has been identified at time of analysis.

Technical ContextAI

The affected component is a PHP-based web application built by code-projects.org (CPE: cpe:2.3:a:code-projects:online_voting_system:*:*:*:*:*:*:*:*). The test_input function in /authentication.php is responsible for preprocessing login credentials but fails to sanitize or parameterize user-supplied input before constructing SQL queries. This is a textbook CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) flaw: without prepared statements or proper escaping, an attacker-controlled string such as ' OR '1'='1 in the username or password field alters the query's logical structure, bypassing the authentication check entirely or causing the database to return arbitrary result sets. The attack surface is the internet-facing login page, requiring no prior authentication or application knowledge.

RemediationAI

No vendor-released patch has been identified at time of analysis. The authoritative source for this vulnerability is VulDB (https://vuldb.com/vuln/376161), and no fix commit or patched release is referenced in available data. Organizations running this application should immediately replace the unsanitized string interpolation in test_input within /authentication.php with PHP PDO or MySQLi prepared statements, which fully neutralize SQL injection regardless of input content. As an interim compensating control, deploying a web application firewall rule to block common SQL injection patterns (e.g., OWASP ModSecurity Core Rule Set) on the /authentication.php endpoint can reduce risk but is not a substitute for a code fix, as WAF rules can be bypassed. If the application is not required to be internet-facing, restricting access to /authentication.php by source IP at the network or web server level eliminates remote exploitation. Given the product's origin as a demonstration/academic project, organizations should evaluate whether this application should be deployed in any production context.