CVE-2025-9656
BaseFortify
Publication date: 2025-08-29
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 | directory_management_system | 2.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9656 is a Cross Site Scripting (XSS) vulnerability in PHPGurukul Directory Management System version 2.0, specifically in the /admin/add-directory.php file. It occurs because the 'fullname' parameter is not properly sanitized, allowing attackers to inject malicious JavaScript code. This code executes in the browsers of users who view the affected page, potentially leading to session hijacking, unauthorized actions, and exposure of sensitive information. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to attackers executing arbitrary scripts in users' browsers, resulting in session hijacking, unauthorized actions, information disclosure, defacement, and theft of sensitive data. The attack can be initiated remotely without requiring authentication, making it easier for attackers to compromise user data and system integrity. [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/add-directory.php endpoint for cross-site scripting (XSS) in the 'fullname' parameter. A proof-of-concept POST request injecting a script payload such as fullname=<script>alert(1)</script> can be used to verify the vulnerability. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:admin/add-directory.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include employing prepared statements and parameter binding to separate user input from executable code, implementing rigorous input validation and filtering to ensure inputs conform to expected formats and block malicious content, and minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. These measures help protect user data, prevent privilege escalation, and maintain system integrity by mitigating the XSS risk. [2, 1]