CVE-2025-9610
BaseFortify
Publication date: 2025-08-29
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-9610 is a critical SQL injection vulnerability in version 1.0 of the code-projects Online Event Judging System, specifically in the /create_account.php file. The vulnerability arises from improper handling of the 'fname' parameter, which is used directly in SQL queries without adequate input validation or sanitization. This allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized database access, data leakage, data manipulation, and potentially full system control or service disruption. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to retrieve sensitive information, modify or delete data, and disrupt system availability. Attackers can perform various SQL injection techniques such as boolean-based blind, error-based, and time-based blind injections. This can result in data leakage, data manipulation, full system compromise, and service disruption, severely impacting the confidentiality, integrity, and availability of the system. [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 /create_account.php endpoint, specifically the 'fname' parameter, for SQL injection. Tools like sqlmap can be used to automate detection. For example, running a command such as: sqlmap -u "http://target/create_account.php" --data="fname=test" -p fname --dbs can confirm exploitability. Additionally, attackers may be identified by monitoring for unusual SQL error messages or time delays caused by injection payloads like 'SLEEP()'. Google dorking with queries like "inurl:create_account.php" can help identify vulnerable targets externally. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input; 2) Applying strict input validation and filtering on the 'fname' parameter and other inputs to ensure they conform to expected formats; 3) Minimizing database user permissions by avoiding high-privilege accounts for routine operations; 4) Conducting regular security audits to detect and fix vulnerabilities promptly. If possible, replacing the affected component with a secure alternative is recommended. These actions help prevent SQL injection attacks and protect data integrity. [1, 3, 2]