CVE-2025-12256
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-12256 is a critical SQL injection vulnerability in version 1.0 of the Online Event Judging System, specifically in the edit_contestant.php file. The vulnerability occurs because the application directly uses user input from the 'contestant_id' parameter in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, potentially gaining unauthorized access to the database, leaking or tampering with data, taking full control of the system, or disrupting services. [1]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, data leakage, data tampering, full system control by attackers, and potential service disruption. Exploiting the vulnerability remotely, attackers can manipulate the database through SQL injection, leading to compromised confidentiality, integrity, and availability of the system and its data. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'contestant_id' parameter in the 'edit_contestant.php' file for SQL injection. A common approach is to use sqlmap with crafted HTTP POST requests targeting this parameter to confirm the presence of SQL injection. For example, you can run a command like: sqlmap -u "http://targetsite/edit_contestant.php" --data="contestant_id=1" --risk=3 --level=5 --batch to test for injection vulnerabilities. [1]
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 'contestant_id' parameter, minimizing database user privileges by avoiding the use of high-privilege accounts for routine database operations, and conducting regular security audits to detect and address vulnerabilities promptly. [1]