Skip to main content
CVE-2025-12252VulnerabilityPublished

CVE-2025-12252: code-projects Online Event Judging System · SQL Injection

Affects code-projects Online Event Judging SystemSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
code-projects Online Event Judging SystemAffected
  • =1.0
Fixed in–

AI-suggested

1. Conduct immediate code review focusing on the /ajax/action.php file to identify and fix the SQL injection flaw by implementing parameterized queries or prepared statements for all database interactions involving user input. 2. Apply strict input validation and sanitization on the 'content' parameter and any other user-supplied data to prevent injection of malicious SQL code. 3. Deploy a Web Application Firewall (WAF) with custom rules to detect and block SQL injection patterns targeting the vulnerable endpoint. 4. Restrict network access to the Online Event Judging System, limiting exposure to trusted internal networks or VPNs to reduce remote attack surface. 5. Monitor database logs and application logs for unusual query patterns or errors indicative of injection attempts. 6. Develop and test patches in a staging environment before production deployment to ensure stability and security. 7. Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases. 8. If possible, isolate the judging system from critical infrastructure to contain potential breaches. 9. Plan for incident response readiness in case exploitation is detected.

Description

A vulnerability was found in code-projects Online Event Judging System 1.0. Affected is an unknown function of the file /ajax/action.php. The manipulation of the argument content results in sql injection. The attack can be launched remotely. The exploit has been made public and could be used.

References

Community reviews

Loading reviews…