CVE-2025-5668
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-5668 is a critical SQL injection vulnerability in the PHPGurukul Medical Card Generation System version 1.0. It exists in the /admin/readenq.php file, specifically in the handling of the "id" parameter. This parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This enables attackers to manipulate SQL queries and perform unauthorized database operations remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and service disruption. Attackers can manipulate SQL queries to execute arbitrary commands, potentially compromising the confidentiality, integrity, and availability of the system. This poses significant risks to system security and business continuity. [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 "id" parameter in the /admin/readenq.php file for SQL injection. Tools like sqlmap can be used to automate detection. For example, running sqlmap against the URL with the vulnerable parameter can confirm the injection: sqlmap -u "http://target/admin/readenq.php?id=1" --batch. Additionally, Google Dorking can help identify vulnerable targets using queries like: inurl:admin/readenq.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the "id" parameter, and restricting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. Since no official patches or countermeasures are published, replacing the affected software with an alternative product is also suggested to avoid exploitation. [2, 3]