CVE-2025-7540
BaseFortify
Publication date: 2025-07-13
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-7540 is a critical SQL injection vulnerability in the Online Appointment Booking System version 1.0, specifically in the /getclinic.php file. The vulnerability occurs because the 'townid' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of database queries, such as viewing, modifying, or deleting sensitive data, without requiring authentication. The flaw arises from constructing SQL commands using externally influenced input without neutralizing special characters. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, modification or deletion of data, potential full system compromise, and disruption of services. Since exploitation requires no authentication and can be done remotely, attackers can easily exploit this flaw to compromise 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 /getclinic.php endpoint for SQL injection via the 'townid' parameter. You can use tools like sqlmap to automate detection, for example: sqlmap -u "http://target/getclinic.php?townid=1" --batch. Manual testing can include sending payloads such as 'townid=CST' AND 4442=4442 AND 'KWmA'='KWmA' to check for boolean-based blind SQL injection, or time-based payloads like 'townid=CST' AND (SELECT SLEEP(5))-- -' to observe response delays. Additionally, Google dorking with the query "inurl:getclinic.php" can help identify vulnerable targets. [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 'townid' parameter, and minimizing database user privileges by avoiding high-privilege accounts for the application database connection. Since no known countermeasures are reported, replacing the affected software with an alternative product is also suggested. Conducting regular security audits to detect and address vulnerabilities promptly is recommended. [2, 3, 1]