Skip to main content

CVE-2025-10103: SQL Injection in code-projects Online Event Judging System

Medium
VulnerabilityCVE-2025-10103cvecve-2025-10103
Published: Mon Sep 08 2025 (09/08/2025, 19:02:07 UTC)
Source: CVE Database V5
Vendor/Project: code-projects
Product: Online Event Judging System

Description

A weakness has been identified in code-projects Online Event Judging System 1.0. This impacts an unknown function of the file /home.php. Executing manipulation of the argument main_event can lead to sql injection. The attack may be performed from remote. The exploit has been made available to the public and could be exploited.

AI-Powered Analysis

AILast updated: 09/08/2025, 19:31:32 UTC

Technical Analysis

CVE-2025-10103 is a SQL Injection vulnerability identified in version 1.0 of the code-projects Online Event Judging System, specifically affecting an unknown function within the /home.php file. The vulnerability arises from improper sanitization or validation of the 'main_event' parameter, which an attacker can manipulate remotely without requiring authentication or user interaction. Exploiting this flaw allows an attacker to inject malicious SQL code into the backend database queries, potentially leading to unauthorized data access, data modification, or even deletion. The vulnerability has a CVSS 4.0 base score of 6.9, indicating a medium severity level. The attack vector is network-based (remote), with low attack complexity and no privileges or user interaction needed. The impact on confidentiality, integrity, and availability is rated as low individually but collectively can lead to significant compromise depending on the database contents and system usage. Although no public exploits are currently known in the wild, the exploit code has been made publicly available, increasing the risk of exploitation. The lack of a patch or mitigation guidance from the vendor at this time further elevates the threat. Given that the Online Event Judging System is likely used to manage event-related data, including participant scores and event details, exploitation could undermine the integrity of event results and expose sensitive participant information.

Potential Impact

For European organizations using the code-projects Online Event Judging System, this vulnerability poses a risk of unauthorized access to sensitive event data, including participant information and judging results. This could lead to data breaches violating GDPR regulations, resulting in legal and financial penalties. The integrity of event outcomes could be compromised, damaging organizational reputation and trust. Additionally, if the backend database contains personally identifiable information (PII) or other sensitive data, attackers could exfiltrate or manipulate this data. The remote and unauthenticated nature of the exploit increases the risk of automated attacks, especially if the system is exposed to the internet. Disruption of event operations due to data corruption or denial of service could also impact business continuity. Organizations in sectors such as education, sports, cultural event management, and corporate event hosting in Europe could be particularly affected.

Mitigation Recommendations

European organizations should immediately conduct an audit to identify any deployments of the code-projects Online Event Judging System version 1.0. Until an official patch is released, implement the following mitigations: 1) Apply Web Application Firewall (WAF) rules to detect and block SQL injection attempts targeting the 'main_event' parameter, using signature-based and anomaly detection methods. 2) Employ input validation and sanitization at the application level, ensuring that all user-supplied inputs, especially 'main_event', are strictly validated against expected formats and escaped properly before database queries. 3) Restrict network exposure of the Online Event Judging System to trusted internal networks or VPNs to reduce attack surface. 4) Monitor logs for suspicious activities related to the 'main_event' parameter and unusual database query patterns. 5) Prepare for rapid patch deployment by establishing communication channels with the vendor or community for updates. 6) Consider isolating the affected system in a segmented network zone to limit potential lateral movement. 7) Conduct regular backups of event data to enable recovery in case of data corruption or loss. These steps go beyond generic advice by focusing on immediate protective controls and operational readiness in the absence of a vendor patch.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-09-08T13:43:20.320Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68bf2ba8d5a2966cfc82975e

Added to database: 9/8/2025, 7:16:56 PM

Last enriched: 9/8/2025, 7:31:32 PM

Last updated: 9/10/2025, 3:10:21 AM

Views: 12

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats