CVE-2025-10102
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-10102 is a critical SQL injection vulnerability in version 1.0 of the code-projects Online Event Judging System, specifically in the /index.php file. The vulnerability occurs because the 'username' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables unauthorized access to the database, potentially allowing attackers to view, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data manipulation, full system compromise, and potential service disruption. Attackers can remotely execute SQL injection attacks without authentication, which may result in loss of data confidentiality, integrity, and availability, severely impacting system security and business continuity. [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 'username' parameter in the /index.php file for SQL injection. Tools like sqlmap can be used to automate detection by sending crafted payloads targeting the username parameter. Example payloads include boolean-based blind, error-based, stacked queries, and time-based blind injections. A sample sqlmap command to test the login endpoint with POST data targeting the username parameter is: sqlmap -u "http://target/index.php" --data="username=admin&password=any" --risk=3 --level=5 --batch. Additionally, Google dorking with queries like "inurl:index.php" can help identify potentially vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product if possible. If replacement is not feasible, implement prepared statements with parameter binding to separate SQL code from user input, apply strict input validation and filtering on the username parameter, and minimize database user permissions to avoid using high-privilege accounts for routine operations. Conduct regular security audits to detect and remediate vulnerabilities promptly. These measures help prevent exploitation of the SQL injection vulnerability. [2, 3, 1]