CVE-2025-5670
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-5670 is a critical SQL injection vulnerability in PHPGurukul Medical Card Generation System version 1.0, specifically in the /admin/manage-card.php file. The vulnerability occurs because the 'id' parameter is directly embedded into SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This enables attackers to manipulate SQL queries arbitrarily and perform unauthorized database operations remotely. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data tampering, and potentially full system compromise or service disruption. Attackers can manipulate SQL queries to access or modify sensitive information, disrupt services, or gain further control over the system. The vulnerability can be exploited remotely without authentication, increasing the risk of attack. [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/manage-card.php file for SQL injection. One method is to send crafted HTTP GET requests with SQL injection payloads, such as: /mcgs/admin/manage-card.php?id=6';SELECT SLEEP(5)#&del=delete to observe delayed server responses indicating injection. Additionally, tools like sqlmap can be used to automate detection of this SQL injection vulnerability. Google dorking with the query inurl:admin/manage-card.php can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats and block malicious data. 3) Restrict database user permissions to the minimum necessary, avoiding high-privilege accounts like 'root' or 'admin' for routine operations. If possible, replace the affected product with an alternative. These measures are critical to protect system security and maintain data integrity. [2, 3]