CVE-2025-12254
BaseFortify
Publication date: 2025-10-27
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| carmelo | online_event_judging_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-12254 is a SQL injection vulnerability in version 1.0 of the code-projects Online Event Judging System, specifically in the /add_judge.php file. The vulnerability occurs because the application improperly handles the 'fullname' parameter, directly incorporating user input into SQL queries without proper sanitization or validation. This allows an attacker to inject malicious SQL code remotely, potentially modifying or manipulating the database. It is classified as a time-based blind SQL injection affecting MySQL 5.0.12 and above, and a proof-of-concept exploit is publicly available. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing unauthorized database access, data leakage, data modification or deletion, full system compromise, and potential service disruption. Because the SQL injection can be exploited remotely, attackers can manipulate the database to alter or destroy data, compromise system integrity, and disrupt business continuity. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'fullname' parameter in the /add_judge.php file for SQL injection. Automated tools like sqlmap can be used to confirm the presence of the SQL injection flaw. A proof-of-concept involves injecting time-based blind SQL injection payloads such as 'SLEEP(5)' through the 'fullname' parameter and observing delayed responses to infer database behavior. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'fullname' parameter, minimizing database user privileges by avoiding use of high-privilege accounts for routine operations, and conducting regular security audits of code and systems. Since no known countermeasures are documented, replacing the affected component with an alternative product is also suggested. [1, 3]