CVE-2025-7601
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-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
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/student-history.php page for reflected cross-site scripting (XSS) via the 'stdid' parameter. One method is to inject a test payload such as `<script>alert(document.cookie);</script>` into the 'stdid' parameter and observe if the script executes in the browser. Additionally, vulnerable targets can be identified using Google dorking with the query: `inurl:admin/student-history.php`. For example, you can use curl or wget to send a request with the payload and check the response for script execution or reflected input. Example command: `curl 'http://targetsite.com/admin/student-history.php?stdid=<script>alert(document.cookie);</script>'` and then verify if the script is reflected in the response. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding use of the vulnerable PHPGurukul Online Library Management System version 3.0 or replacing it with an alternative product, as no known countermeasures or patches have been reported. Additionally, restricting access to the /admin/student-history.php page, applying web application firewall (WAF) rules to block malicious input in the 'stdid' parameter, and educating users to avoid clicking suspicious links can help reduce risk until a fix is available. [2]
Can you explain this vulnerability to me?
This vulnerability is a Cross-Site Scripting (XSS) flaw in the PHPGurukul Online Library Management System version 3.0, specifically in the /admin/student-history.php file. It occurs because the 'stdid' parameter is not properly sanitized or validated, allowing an attacker to inject malicious JavaScript code. When a user visits the affected page with a crafted 'stdid' parameter, the injected script executes in their browser, potentially compromising their security and privacy. [1, 2, 3]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to execute arbitrary scripts in the context of your web application. This can lead to theft of sensitive information such as cookies, session tokens, or other data accessible to the browser, potentially compromising user accounts and privacy. The attack can be initiated remotely and requires user interaction, making it a risk for users who visit the affected page with malicious input. [1, 2, 3]