CVE-2025-7587
BaseFortify
Publication date: 2025-07-14
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-7587 is a critical SQL injection vulnerability in version 1.0 of the Online Appointment Booking System, specifically in the /cover.php file. The vulnerability occurs because the uname and psw parameters are not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, enabling them to execute arbitrary SQL commands on the database. This can lead to unauthorized access, data leakage, modification, or deletion of sensitive information. [1, 2, 3, 4]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to read, modify, or delete sensitive data. It can result in full system compromise and potential service disruption. Attackers can extract confidential information, alter data integrity, and affect the availability of the system. The vulnerability can be exploited remotely without any authentication, making it highly dangerous. [1, 2, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable parameters 'uname' and 'psw' in the /cover.php file for SQL injection. Tools like sqlmap can be used to automate detection by sending crafted requests targeting these parameters. Example payloads include boolean-based blind injections (e.g., uname=-8837' OR 1020=1020 #), error-based injections using MySQL functions, time-based blind injections, and UNION query injections. Additionally, Google dorking with queries such as inurl:cover.php can help locate vulnerable targets. [3, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering on the 'uname' and 'psw' parameters, minimizing database user permissions by avoiding high-privilege accounts for application database connections, and conducting regular security audits of code and systems. Since no known mitigations or countermeasures are documented, replacing the affected software with an alternative product is also suggested. [3, 4, 1, 2]