CVE-2025-9766
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?
This vulnerability is a SQL injection flaw in the Sports Management System version 1.0, specifically in the /Admin/facilitator.php file. It occurs because the application uses the 'code' parameter from POST requests directly in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely without authentication, potentially accessing, modifying, or deleting database information and even gaining full system control. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, data leakage, data modification or deletion, full system compromise, and potential disruption of services. Attackers can manipulate the database remotely without needing to authenticate, which poses a severe risk to system security and business continuity. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable parameter `code` in POST requests to the /Admin/facilitator.php file for SQL injection. You can use tools like sqlmap to automate detection and exploitation. Example sqlmap command: sqlmap -u "http://target/Admin/facilitator.php" --data="code=TOUR-105&name=1111&submit=Save" -p code --dbms MySQL. Additionally, manual testing with payloads such as error-based or time-based blind SQL injection strings can be used to confirm the vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection. 2) Apply strict input validation and filtering on the `code` parameter to ensure it matches expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for the application's database connections. 4) Conduct regular security audits to detect and fix vulnerabilities promptly. [1]