CVE-2025-7752
BaseFortify
Publication date: 2025-07-17
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 |
|---|---|---|
| anisha | online_appointment_booking_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-7752 is a critical SQL injection vulnerability in the Online Appointment Booking System version 1.0, specifically in the /admin/deletedoctor.php file. The vulnerability occurs because the 'did' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data extraction, modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, modification or deletion of database records, and disruption of system operations. Attackers can exploit it remotely without authentication, potentially compromising confidentiality, integrity, and availability of the system. This poses significant risks to data security and business continuity. [1, 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 'did' parameter in the /admin/deletedoctor.php file for SQL injection. A common approach is to use automated tools like sqlmap to test for SQL injection vulnerabilities. For example, the sqlmap command can be used targeting the 'did' parameter to confirm the vulnerability. Additionally, attackers can be identified by monitoring for unusual requests to /admin/deletedoctor.php with suspicious 'did' parameter values. Google dorking with the query 'inurl:admin/deletedoctor.php' can help identify vulnerable targets externally. [2, 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 'did' parameter to ensure it conforms to expected formats. 3) Minimize database user privileges by avoiding use of high-privilege accounts such as root or admin for routine database operations. 4) Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace the affected component with an alternative product as no known mitigations have been reported. [2, 3]