CVE-2025-6333
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 | 2.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-6333 is a critical SQL injection vulnerability in the PHPGurukul Directory Management System version 2.0, specifically in the /admin/admin-profile.php file. The vulnerability occurs because the 'adminname' parameter is not properly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely, potentially manipulating the database in unauthorized ways. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption. Since the attack can be performed remotely without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the system and its data. [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 'adminname' parameter in the /admin/admin-profile.php file for SQL injection. Tools like sqlmap can be used to automate detection, for example by sending payloads targeting the 'adminname' POST parameter. Additionally, Google dorking with queries such as 'inurl:admin/admin-profile.php' can help identify potentially vulnerable targets. A sample command using sqlmap might be: sqlmap -u "http://target/admin/admin-profile.php" --data="adminname=Admin" --technique=BEUSTQ to test for SQL injection. [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) Applying strict input validation and filtering on the 'adminname' parameter to ensure inputs conform to expected formats; 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations; and 4) Considering replacing the affected component with an alternative product if feasible. [2, 3]