CVE-2025-5638
BaseFortify
Publication date: 2025-06-05
Last updated on: 2025-06-06
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | notice_board_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-5638 is a critical SQL injection vulnerability in the PHPGurukul Notice Board System version 1.0, specifically in the /admin-profile.php file. The vulnerability occurs because the 'mobilenumber' 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 such as accessing, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to perform unauthorized database operations, including data leakage, data manipulation, and potentially full system compromise or service disruption. Since the attack can be launched remotely and exploits are publicly available, it poses a significant risk to the confidentiality, integrity, and availability of your system and 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 'mobilenumber' parameter in the /admin-profile.php file for SQL injection. Tools like sqlmap can be used to automate detection by targeting this parameter. Example sqlmap command: sqlmap -u "http://target/admin-profile.php" --data="mobilenumber=123" -p mobilenumber --level=5 --risk=3. Additionally, manual testing can be done using boolean-based blind or time-based blind SQL injection payloads, such as injecting '1233211231' AND 5486=(SELECT (CASE WHEN (5486=5486) THEN 5486 ELSE (SELECT 8946 UNION SELECT 4242) END))-- -' or using time delays with MySQL's SLEEP function in the mobilenumber parameter to observe response delays. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Enforce strict input validation and filtering on the 'mobilenumber' parameter to ensure it conforms to expected formats. 3) Minimize database user privileges by avoiding the use of high-privilege accounts for routine database operations. Additionally, consider replacing the affected software with an alternative product as no known countermeasures are documented. [2, 3]