CVE-2025-9802
BaseFortify
Publication date: 2025-09-02
Last updated on: 2025-09-02
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| remoteclinic | remoteclinic | 2.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?
CVE-2025-9802 is a Boolean-Based Blind SQL Injection vulnerability in RemoteClinic version 2.0, specifically in the file /staff/profile.php via the 'id' parameter. The backend code fails to properly sanitize or filter the 'id' parameter, directly concatenating user input into SQL queries. This allows attackers to inject SQL code by manipulating the 'id' parameter, enabling them to execute unauthorized SQL commands remotely. The vulnerability arises because of improper input validation and lack of parameterized queries. [1, 3]
How can this vulnerability impact me? :
This vulnerability can lead to several serious impacts including data breaches where attackers can extract sensitive information such as user passwords and personal details; data tampering where attackers can modify database contents including user permissions; data deletion causing loss of important data and disruption of application operations; and potentially execution of malicious code if the database supports such features, which could lead to full server compromise. [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 'id' parameter in the /staff/profile.php URL for SQL injection using Boolean-based blind SQL injection payloads. For example, you can manipulate the URL parameter with payloads like ' AND 1=1--+ and ' AND 1=2--+ to observe different page responses indicating injection feasibility. Additionally, tools like SQLMAP can be used to automate detection by targeting the vulnerable parameter. A sample manual test command using curl might be: curl 'http://target/staff/profile.php?id=1' and then curl 'http://target/staff/profile.php?id=1'" AND 1=2--+" to compare responses. Also, Google dorking with queries such as inurl:staff/profile.php can help identify potentially vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing parameterized queries to prevent SQL injection by separating SQL code from user input, strictly validating and sanitizing the 'id' parameter to allow only valid characters, and limiting database user permissions to the minimum necessary for the application. If possible, replace the affected component with an alternative product. Since no public exploit currently exists, applying these mitigations promptly will reduce risk. [1, 2]