CVE-2025-9788
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 |
|---|---|---|
| campcodes | school_log_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-9788 is a critical SQL injection vulnerability in the CampCodes School Log Management System version 1.0, specifically in the /admin/admin_class.php file. The vulnerability arises because the 'id_no' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to manipulate, delete, or extract sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to modify, delete, or expose sensitive information. It can also enable attackers to disrupt system availability or potentially take full control of the system, threatening data integrity, confidentiality, 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 'id_no' parameter in the /admin/admin_class.php file for SQL injection. A proof-of-concept involves sending a time-based blind SQL injection payload such as: id_no=1' AND (SELECT 7104 FROM (SELECT(SLEEP(5)))TEjS) AND 'umot'='umot to observe a delay in server response. Additionally, tools like sqlmap can be used to automate detection by crafting POST requests targeting the 'id_no' parameter to enumerate databases and confirm injection points. Attackers may also identify vulnerable targets using Google dorking with queries like "inurl:admin/admin_class.php". [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to separate SQL code from user input, preventing injection; 2) Implementing strict input validation and filtering to ensure user inputs conform to expected formats; 3) Minimizing database user permissions by avoiding high-privilege accounts for routine operations; 4) Conducting regular security audits of code and systems to detect and address vulnerabilities promptly. Since no known countermeasures or patches are documented, replacing the affected component with an alternative product is also recommended. [2, 3]