CVE-2025-14833
BaseFortify
Publication date: 2025-12-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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection flaw in the Online Appointment Booking System 1.0 by code-projects. It exists in an unknown function within the file /admin/deletemanagerclinic.php. By manipulating the 'clinic' argument, an attacker can perform SQL injection remotely, potentially allowing unauthorized database access or manipulation. The exploit is publicly available.
How can this vulnerability impact me? :
The vulnerability can allow remote attackers to execute arbitrary SQL commands on the database, leading to unauthorized data access, data modification, or deletion. This can compromise the integrity, confidentiality, and availability of the system's data and may result in service disruption or data breaches.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information regarding the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.
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/deletemanagerclinic.php file for SQL injection. Example payloads include error-based and time-based blind SQL injection tests. For instance, sending POST requests with payloads such as: 1) Error-based injection: city=Mumbai&clinic=1 AND GTID_SUBSET(CONCAT(0x716a626a71,(SELECT (ELT(7053=7053,1))),0x7170717871),7053)-- 2) Time-based blind injection: city=Mumbai&clinic=1 AND 3663=(SELECT COUNT(*) FROM INFORMATION_SCHEMA.COLUMNS A, INFORMATION_SCHEMA.COLUMNS B, INFORMATION_SCHEMA.COLUMNS C WHERE 0 XOR 1)-- Additionally, tools like sqlmap can be used to automate detection of this SQL injection vulnerability by targeting the 'clinic' parameter in the specified URL. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering to ensure parameters conform to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and address vulnerabilities promptly. These steps help protect system security and data integrity against exploitation of this SQL injection vulnerability. [1]