CVE-2025-7751
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-7751 is a critical SQL injection vulnerability in the Online Appointment Booking System version 1.0, specifically in the /admin/addclinic.php file. It occurs because the 'cid' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This lets attackers manipulate database queries, potentially accessing, modifying, or deleting sensitive data without authorization. The vulnerability can be exploited remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to gain unauthorized access to your database, leak sensitive information, alter or delete data, and potentially take full control of the system. It can also disrupt service availability. Since exploitation requires no authentication and can be performed remotely, it poses a high risk to confidentiality, integrity, and availability of your system and data. [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 'cid' parameter in the /admin/addclinic.php file for SQL injection. Common detection methods include using SQL injection testing tools like sqlmap. Example commands include: - Boolean-based blind SQL injection test: sending payloads such as cid=11' AND 5633=5633 AND 'TKmp'='TKmp - Error-based SQL injection test on MySQL >= 5.6 using functions like GTID_SUBSET - Time-based blind SQL injection test on MySQL >= 5.0.12 using SLEEP() function to observe delays Additionally, attackers may identify vulnerable targets using Google dorking with the query: inurl:admin/addclinic.php [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. - Enforce strict input validation and filtering on the 'cid' parameter to ensure it conforms to expected formats. - Minimize database user privileges by avoiding use of high-privilege accounts (e.g., root or admin) for routine database operations. - Consider replacing the affected component with an alternative product if possible. - Conduct regular security audits to detect and address vulnerabilities promptly. These steps help secure the system, protect data integrity, and maintain business continuity. [1, 2, 3]