CVE-2025-9767
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-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-9767 is a critical SQL injection vulnerability in itsourcecode Sports Management System version 1.0, specifically in the /Admin/sporttype.php file. The vulnerability occurs because the 'code' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL queries. This can lead to unauthorized access to the database, data leakage, modification, or deletion. The attack can be performed remotely without authentication, making it easy to exploit. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to sensitive data, modification or deletion of database contents, and potentially full system compromise or service disruption. Since the attack requires no authentication and can be executed remotely, it poses a significant risk to data confidentiality, integrity, and availability. This can result in data breaches, loss of business continuity, and damage to the organization's reputation. [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/sporttype.php endpoint, specifically the 'code' parameter, for SQL injection flaws. Tools like sqlmap can be used to automate detection. For example, running sqlmap against the URL with the vulnerable parameter can confirm exploitability. Additionally, Google dorking with the query 'inurl:Admin/sporttype.php' can help identify vulnerable targets. Proof-of-concept payloads include error-based and time-based blind SQL injection techniques using MySQL functions such as GTID_SUBSET and SLEEP. [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, enforcing strict input validation and filtering on the 'code' parameter, and minimizing database user privileges by avoiding use of high-privilege accounts for routine operations. Regular security audits should be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected component with an alternative product is suggested as no known countermeasures have been reported. [1, 2, 3]