CVE-2025-7600
BaseFortify
Publication date: 2025-07-14
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 |
|---|---|---|
| phpgurukul | online_library_management_system | 3.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-7600 is a critical SQL injection vulnerability in the PHPGurukul Online Library Management System version 3.0, specifically in the /admin/student-history.php file. The vulnerability arises because the stdid parameter is not properly sanitized or validated before being used in SQL queries. This allows remote attackers to inject malicious SQL code, potentially manipulating the database queries executed by the system. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to gain unauthorized access to the database, leak sensitive data, manipulate or delete data, and potentially compromise the entire system. Exploitation techniques include Boolean-based blind SQL injection, stacked queries, time-based blind SQL injection, and UNION-based SQL injection. The impact includes loss of confidentiality, integrity, and availability of the system, which can severely affect 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 'stdid' parameter in the /admin/student-history.php page for SQL injection. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/admin/student-history.php?stdid=SID001" --batch --dbs. Additionally, manual testing can be done using payloads such as 'stdid=SID002' AND 1994=1994--' (Boolean-based), 'stdid=SID002';SELECT SLEEP(5)#' (stacked queries), or time-based payloads like 'stdid=SID002' AND (SELECT 9250 FROM (SELECT(SLEEP(5)))LDjI)--'. Google dork queries like inurl:admin/student-history.php can help identify vulnerable targets. [1, 2]
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 'stdid' parameter to ensure it conforms to expected formats, and minimizing database user privileges by avoiding the use of high-privilege accounts for routine database operations. Since no known countermeasures are documented, replacing the affected component with an alternative product is also suggested. [1, 2]