CVE-2025-6308
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 | emergency_ambulance_hiring_portal | 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-6308 is a critical SQL injection vulnerability in the PHPGurukul Emergency Ambulance Hiring Portal version 1.0. It exists in the file /admin/bwdates-request-report-details.php, specifically involving the 'fromdate' and 'todate' parameters. These parameters are not properly sanitized or validated before being used in SQL queries, allowing attackers to inject malicious SQL code remotely without authentication. This enables attackers to manipulate database queries, potentially accessing, modifying, or deleting sensitive data. [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 extract sensitive information, modify or delete data, and possibly gain control over the affected system, severely impacting system confidentiality, integrity, and availability. [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 vulnerable endpoint /admin/bwdates-request-report-details.php for SQL injection in the 'todate' and 'fromdate' parameters. Example detection commands include sending crafted POST requests with payloads such as: - Boolean-based blind: fromdate=2000-01-01&todate=2025-06-01' AND 6708=6708-- - Time-based blind: fromdate=2000-01-01&todate=2025-06-01' AND (SELECT SLEEP(5))-- - UNION query: fromdate=2000-01-01&todate=2025-06-01' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,CONCAT(0x716b627071,0x707a4d55766e587a4150457656464b4e4c6a4f756c595858745a7564416756625051615a754b6349,0x71766a7071),NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL-- Additionally, the vulnerability can be detected using sqlmap tool targeting the vulnerable POST parameters. Google dorking can also identify vulnerable targets using the query: inurl:admin/bwdates-request-report-details.php [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input. - Apply strict input validation and filtering on the 'fromdate' and 'todate' parameters to ensure they conform to expected date formats. - Limit database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. Since no known countermeasures are reported and replacement of the affected component is recommended, consider updating or replacing the vulnerable software version as a longer-term solution. [2, 3]