CVE-2025-5669
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 | medical_card_generation_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-5669 is a critical SQL injection vulnerability in the PHPGurukul Medical Card Generation System version 1.0, specifically in the /admin/unreadenq.php file. The vulnerability occurs because the 'id' parameter is not properly sanitized or validated before being used in SQL queries, allowing attackers to inject malicious SQL code. This can be exploited remotely without authentication, enabling attackers to manipulate database queries arbitrarily. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to perform unauthorized database operations such as data leakage, data tampering, full system compromise, and service disruption. Attackers can execute arbitrary SQL commands, including stacked queries, which can lead to loss of confidentiality, integrity, and availability of the system. The exploit is publicly available and can be triggered remotely, increasing the risk of attack. [1, 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/unreadenq.php endpoint for SQL injection on the 'id' parameter. Tools like sqlmap can be used to identify the injection point and verify the ability to execute stacked queries. An example command using sqlmap is: sqlmap -u "http://target/mcgs/admin/unreadenq.php?id=2" --batch --dbs. Additionally, Google dorking with queries such as inurl:admin/unreadenq.php can help locate vulnerable targets. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to separate SQL code from user input, preventing injection; 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats; 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations; and 4) Replacing the affected software with an alternative product if possible. [1, 3]