CVE-2025-8925
BaseFortify
Publication date: 2025-08-13
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-8925 is a critical SQL injection vulnerability in itsourcecode Sports Management System version 1.0, specifically in the /Admin/match.php file. The vulnerability arises from improper handling and insufficient validation of the 'code' parameter, which allows attackers to inject malicious SQL queries remotely without authentication. This can lead to unauthorized database access, data modification, deletion, and exposure of sensitive information. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, leakage of sensitive information, unauthorized modification or deletion of data, potential full system compromise, and disruption of services. Since the attack can be performed remotely without authentication, it poses a significant risk to 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 /Admin/match.php endpoint, specifically the 'code' parameter, for SQL injection. You can use tools like sqlmap to automate detection. For example, run a command like: sqlmap -u "http://<target>/Admin/match.php" --data="code=TEST&name=1111&submit=Save" --risk=3 --level=5 --batch to test for SQL injection. Additionally, Google dorking with the query inurl:Admin/match.php can help identify vulnerable targets. Manual testing can include injecting payloads such as error-based or time-based SQL injection strings into the 'code' parameter and observing responses or delays. [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 of code and system configurations should be conducted. Since no known countermeasures or patches are documented, replacing the affected component with an alternative product is also suggested. [2, 3]