CVE-2025-10103: code-projects Online Event Judging System · SQL Injection
Affects code-projects Online Event Judging SystemSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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:PExploitation evidence
Disclosed: evidence found.
CVE published 8 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code-projects Online Event Judging System | Affected
| Fixed in– |
AI-suggested
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.
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.