CVE-2025-6331
BaseFortify
Publication date: 2025-06-20
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 | 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-6331 is a critical SQL injection vulnerability in PHPGurukul Directory Management System version 1.0. It exists in the /admin/search-directory.php file, specifically involving the 'searchdata' parameter. This parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code remotely. Exploiting this flaw enables unauthorized execution of arbitrary SQL commands, potentially leading to unauthorized data access, data manipulation, and full system compromise. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, data tampering, and potential full system compromise. Attackers can remotely execute arbitrary SQL commands, which may disrupt service availability, manipulate or delete data, and gain control over the affected system. [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 'searchdata' parameter in the /admin/search-directory.php file for SQL injection flaws. You can use tools like sqlmap to automate detection. For example, running sqlmap targeting the POST parameter 'searchdata' can reveal the vulnerability. Additionally, manual testing with payloads such as a time-based blind SQL injection payload (e.g., searchdata=111' AND (SELECT SLEEP(5))-- ) can help detect the issue. Google dorking with the query 'inurl:admin/search-directory.php' can help identify vulnerable targets on your network or externally. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Enforcing strict input validation and filtering on the 'searchdata' parameter to ensure inputs conform to expected formats. 3) Restricting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. Since no known countermeasures or patches are documented, replacing the affected product with a secure alternative is also suggested. [2, 3]