CVE-2025-10103
BaseFortify
Publication date: 2025-09-08
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-10103 is a critical SQL injection vulnerability in version 1.0 of the Online Event Judging System, specifically in the /home.php file. It occurs because the 'main_event' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating the database by extracting, modifying, or deleting data. The vulnerability exploits improper handling of special characters in the input, leading to unauthorized database access and control. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, data leakage, data tampering, deletion or modification of data, full system control by attackers, and potential disruption of services. Since it can be exploited remotely without authentication, attackers can compromise the confidentiality, integrity, and availability of the system, leading to significant operational and security risks. [1, 2, 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 'main_event' parameter in the /home.php file for SQL injection. A practical approach is to use automated tools like sqlmap to test for SQL injection by sending crafted payloads to the parameter. For example, using sqlmap with a POST request targeting the main_event parameter can confirm the vulnerability. Additionally, searching for the vulnerable endpoint using Google dorking with queries like "inurl:home.php" can help identify exposed instances. An example payload used to test the injection is: main_event=123123' AND EXTRACTVALUE(2790,CONCAT(0x5c,0x71707a6271,(SELECT (ELT(2790=2790,1))),0x71766b7171)) AND 'wEQJ'='wEQJ [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Applying strict input validation and filtering on the 'main_event' parameter to ensure only expected input formats are accepted. 3) Minimizing database user privileges by avoiding use of high-privilege accounts such as root or admin for routine database operations. 4) Conducting regular security audits of the code and system to detect and fix vulnerabilities promptly. If possible, consider replacing the affected software with an alternative product as no known direct mitigations are available. [1, 3]