An unauthenticated SQL injection vulnerability in the SourceCodester Online Voting System version 1.0 poses a critical risk of unauthorized database access and potential system compromise.

The application is vulnerable to SQL injection via the id parameter in the /ajax.php?action=delete_category endpoint. This vulnerability allows an unauthenticated attacker to inject malicious SQL queries, which are then executed by the database without proper validation.

Successful exploitation of this vulnerability can lead to unauthorized access to the underlying database, enabling attackers to leak sensitive information, modify or delete critical data, and potentially gain full control over the application. Given the nature of a voting system, this compromise could lead to significant reputational damage, loss of data integrity, and disruption of service. While the CVSS score of 7.3 indicates a high severity, the ability for an unauthenticated attacker to manipulate backend queries significantly elevates the risk to business continuity.

Immediate Action: As no official vendor patch is currently available, administrators should restrict access to the affected endpoint at the network or web server level and implement strict input validation for the id parameter.

Proactive Monitoring: Review web server access logs for anomalous POST requests directed at /ajax.php, specifically monitoring for unusual patterns or characters associated with SQL injection payloads.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection attempts targeting the id parameter in application requests.

Public Exploit Available: Yes — a published proof-of-concept exists, attributed to the security researcher write-up linked in the CVE references.

Due to the lack of a vendor-provided patch, users of the SourceCodester Online Voting System 1.0 must prioritize implementing robust compensating controls such as WAF rules and access restrictions. Organizations should treat this as a high-priority risk and transition to a more secure or maintained alternative if the vendor does not release a formal security update to remediate the underlying code flaw.