CVE-2025-9765
BaseFortify
Publication date: 2025-09-01
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 |
|---|---|---|
| angeljudesuarez | sports_management_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-9765 is a critical SQL injection vulnerability in itsourcecode Sports Management System version 1.0, specifically in the /Admin/tournament_details.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, allowing attackers to extract sensitive information, modify or delete data, and disrupt system operations. Since it can be exploited remotely without authentication, it poses a significant risk to data confidentiality, integrity, and availability. Attackers can use various SQL injection techniques to manipulate the database, potentially causing severe damage to the system and its data. [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 /Admin/tournament_details.php endpoint for SQL injection on the 'id' parameter. You can use tools like sqlmap to automate detection. For example, a command to test might be: sqlmap -u "http://targetsite/Admin/tournament_details.php?id=1" --batch --dbs. Additionally, Google dorking can help identify vulnerable targets using queries like: inurl:Admin/tournament_details.php. Manual testing can include injecting SQL payloads such as ' OR '1'='1 or time-based payloads to observe responses. [2, 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 by separating SQL code from user inputs. Enforce strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. Minimize database user permissions, avoiding high-privilege accounts for routine operations. Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace the affected component with an alternative product. [2, 3, 1]