Skip to main content

Online Event Judging System CVE-2025-12255

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
    Obtain valid system credentials
  2. Delivery
    Authenticate to application
  3. Exploit
    Access /add_contestant.php form
  4. Execution
    Inject SQL in fullname parameter
  5. Persist
    Execute unauthorized database query
  6. Impact
    Extract sensitive data

Vulnerability Assessment

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

A valid user account with authentication credentials is required to access the /add_contestant.php endpoint. The vulnerable fullname parameter is only processed when a user is authenticated and submits the contestant registration form. Default configurations likely allow this if the system is not explicitly locked down. No indication exists that the vulnerability is triggered only under specific deployment modes or non-default settings. The attack does not require elevated administrative privileges, only basic authenticated user access.

Impact

This vulnerability presents minimal real-world risk despite public exploit availability. The CVSS 4.0 vector indicates PR:L (login required), AC:L (low complexity), AV:N (network-accessible), but with very limited impact: VC:L/VI:L/VA:L (low confidentiality, integrity, and availability impact on the vulnerable system), and SC:N/SI:N/SA:N (no scope change or impact on other systems). The EPSS score of 0.03% (8th percentile) reflects this assessment-it ranks among the lowest-risk vulnerabilities despite public exploit code. The SQL injection is limited to information disclosure rather than data modification or system compromise. Exploitation requires valid authentication credentials, significantly reducing opportunistic attack likelihood. The primary risk is to organizations running this specific legacy or educational application; broader enterprise environments are unaffected. However, the public exploit availability means any authenticated attacker with system access can trivially extract sensitive data from the database without complex exploitation techniques.

Exploit ScenarioDerived

An authenticated contestant or judge logs into the Online Event Judging System and navigates to the contestant registration page. They modify the fullname parameter to inject a SQL UNION statement in their browser's request, such as fullname='; UNION SELECT password FROM users -- to retrieve password hashes or sensitive user data. The injected SQL executes within the context of the legitimate database query, returning unauthorized information that appears in the application response or logs.

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 fullname parameter in /add_contestant.php, enabling database queries with limited data access. The vulnerability has low real-world risk despite public exploit availability, as it requires valid user authentication and produces only limited information disclosure (CVSS 2.1, EPSS 0.03%), though organizations running this application should apply fixes promptly to eliminate the attack vector entirely.

RemediationAI

Apply vendor updates or patches if available from code-projects or the Carmelo development team. If patched versions are unavailable, implement immediate compensating controls: enforce parameterized prepared statements or prepared queries in the /add_contestant.php file's database interaction code, validate and whitelist the fullname parameter to permit only alphanumeric characters and common punctuation (spaces, hyphens, apostrophes), implement database-level least-privilege access so the application's database user lacks write permissions beyond the contestant table, and deploy a Web Application Firewall (WAF) rule to block requests containing SQL keywords (UNION, SELECT, OR, etc.) in the fullname parameter. Consider disabling or restricting access to the contestant management feature via network access controls or authentication tokens if the application is not actively used. Organizations should coordinate patching with functional testing, as WAF rules may block legitimate names containing special characters.

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 exists in a PHP-based web application that processes contestant registration through the /add_contestant.php endpoint. The application fails to properly sanitize or parameterize the fullname input parameter before incorporating it into SQL queries, allowing an authenticated user to inject arbitrary SQL syntax. This is classified as CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), indicating a failure to escape or filter user-controlled input before database interaction. The affected product is identified by CPE 2.3:a:carmelo:online_event_judging_system:1.0, suggesting a small-scale educational or competition management tool rather than enterprise software.

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 security flaw has been discovered in code-projects Online Event Judging System 1.0. This affects an unknown part of the file /add_contestant.php. Performing manipulation of the argument fullname results in sql injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may 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