Skip to main content

Online Event Judging System CVE-2025-12256

LOW
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') (CWE-74)
2025-10-27 cna@vuldb.com
2.1
CVSS 4.0 · Vendor: vuldb
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to system with valid credentials
  2. Delivery
    Access /edit_contestant.php page
  3. Exploit
    Craft SQL injection payload in contestant_id parameter
  4. Execution
    Submit malicious request
  5. Persist
    Database executes injected SQL
  6. Impact
    Read, modify, or delete data within application's data scope

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Input neutralization, injection prevention
Exploitation Conditions

Authentication is mandatory - attacker must possess valid login credentials (low-privilege user account acceptable per PR:L in CVSS vector). The contestant_id parameter in /edit_contestant.php must accept unsanitized user input and pass it directly into SQL queries without prepared statement protection. Default or non-hardened configurations of the application are vulnerable; no unusual configuration is required. Exploitation is limited to the authenticated user context; privilege escalation is not indicated.

Impact

The risk assessment reveals a significant disconnect between technical severity and real-world exploitability. The CVSS v4.0 score of 2.1 reflects limited impact scope (L/L/L for confidentiality, integrity, availability) and mandatory authentication (PR:L), resulting in minimal severity. The EPSS score of 0.03% (8th percentile) strongly indicates this vulnerability is unlikely to be exploited in practice, placing it well below the exploitation probability threshold for active targeting. Although a public exploit exists (POC available), the authentication requirement is a critical limiting factor - the attacker must possess valid system credentials. The E:P flag (Exploit maturity: Proof-of-Concept) confirms POC availability but not active weaponization or KEV listing. This is a textbook case of high-novelty, low-impact vulnerability: publicly disclosed and PoC-available but operationally constrained by authentication prerequisites and narrow impact scope. Real-world risk is low for organizations with basic access controls.

Exploit ScenarioDerived

An authenticated user (e.g., a contest judge or administrator with valid credentials) navigates to the contestant editing interface and manipulates the contestant_id parameter in the URL or POST data to inject a SQL fragment such as contestant_id=1' OR '1'='1. This causes the SQL query to execute unintended logic, potentially exfiltrating contestant data, modifying records, or determining database structure. Public exploit code is available on GitHub (https://github.com/zzonce/cve/issues/2), lowering the skill barrier for exploitation.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 29, 2026

SQL injection in code-projects Online Event Judging System 1.0 allows authenticated remote attackers to manipulate the contestant_id parameter in /edit_contestant.php, resulting in limited confidentiality, integrity, and availability impact. The vulnerability has a publicly available exploit and low EPSS score (0.03%), suggesting it poses minimal real-world risk despite public exploit availability.

RemediationAI

Apply a vendor patch if available from code-projects (check https://code-projects.org/ for updates beyond version 1.0). If no patched version is available, implement immediate compensating controls: (1) Use parameterized SQL queries (prepared statements) in /edit_contestant.php to neutralize SQL injection, (2) Implement input validation/whitelist for contestant_id to accept only numeric values, (3) Apply Web Application Firewall (WAF) rules to detect and block SQL injection patterns in the contestant_id parameter, (4) Restrict access to the /edit_contestant.php endpoint to trusted administrative networks via IP allowlist if possible. The authentication requirement (PR:L) means unauthorized remote exploitation is not possible, so access control hardening is an effective interim control. Web application code review and security testing of all user-input handling in the application should be prioritized.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is a SQL injection flaw (CWE-74: Improper Neutralization of Special Elements used in an Output) in a PHP-based web application. The /edit_contestant.php file accepts user-supplied input via the contestant_id parameter without proper sanitization or parameterized queries, allowing attackers to inject arbitrary SQL commands. This affects the Online Event Judging System, a PHP web application designed for contest management. The attack vector is network-based, but requires valid authentication (PR:L in CVSS vector indicates low-privilege authenticated access).

Know when Online Event Judging System gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vuldb) PRIMARY 2.1 LOW
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

Primary rating from Vendor (vuldb) · only source for this CVE.

CVSS VectorVendor: vuldb

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A weakness has been identified in code-projects Online Event Judging System 1.0. This vulnerability affects unknown code of the file /edit_contestant.php. Executing manipulation of the argument contestant_id can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could be exploited.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Low

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

Affected Products (CPE)CVE.org

cpe:2.3:a:carmelo:online_event_judging_system:1.0:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy