CVE-2025-7750
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-7750 is a critical SQL injection vulnerability in the Online Appointment Booking System version 1.0, specifically in the /admin/adddoctorclinic.php file. It occurs because the 'clinic' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. The vulnerability can be exploited using error-based or time-based blind SQL injection techniques. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, resulting in data leakage, modification, or deletion. Attackers can compromise the confidentiality, integrity, and availability of the system's data. It may also lead to full system compromise or service disruption, posing significant risks to system 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 'clinic' parameter in the /admin/adddoctorclinic.php file for SQL injection. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/admin/adddoctorclinic.php?clinic=1" --risk=3 --level=5 --batch. Additionally, manual testing can be done using proof-of-concept payloads such as error-based or time-based blind SQL injection payloads. For example, sending a request with the parameter clinic=1' AND (SELECT SLEEP(5)) AND '1'='1 to observe delayed responses indicating vulnerability. Google dorking can also help identify vulnerable targets using queries like inurl:admin/adddoctorclinic.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, applying strict input validation and filtering on the 'clinic' parameter, and minimizing database user privileges by avoiding high-privilege accounts for routine operations. Since no known mitigations or patches are reported, replacing the affected component with an alternative product is suggested. Conducting regular security audits to detect and address vulnerabilities promptly is also recommended. [2, 3]