VulnerabilityPublished 1 Sep 2025

CVE-2025-9802: RemoteClinic · SQL Injection

Affects RemoteClinicSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
RemoteClinic	Affected =2.0	Fixed in–

AI-suggested

1. Immediate mitigation should include restricting access to the /staff/profile.php endpoint to trusted and authenticated users only, ideally with multi-factor authentication to reduce the risk of compromised credentials. 2. Implement input validation and parameterized queries or prepared statements in the code handling the 'ID' parameter to prevent SQL injection. 3. Conduct a thorough code review of RemoteClinic 2.0 to identify and remediate any other unsanitized inputs. 4. Monitor logs for unusual database queries or access patterns that could indicate exploitation attempts. 5. Network segmentation should be enforced to isolate RemoteClinic servers from broader enterprise networks, limiting attacker lateral movement. 6. Until an official patch is released, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting this endpoint. 7. Educate staff on the importance of credential security and monitor for compromised accounts. 8. Plan for timely patch management once a fix becomes available from the vendor.

Description

A vulnerability was detected in RemoteClinic 2.0. This vulnerability affects unknown code of the file /staff/profile.php. The manipulation of the argument ID results in sql injection. The attack can be executed remotely.

Impact

For European organizations using RemoteClinic 2.0, this vulnerability poses a risk to the confidentiality and integrity of sensitive staff and patient data. Healthcare providers are subject to strict data protection regulations such as GDPR, and any unauthorized access or data manipulation could lead to regulatory penalties, reputational damage, and loss of patient trust. The ability to remotely exploit this vulnerability means attackers could potentially compromise internal staff profiles, leading to privilege escalation or lateral movement within the network. Although the CVSS score indicates a medium severity with limited impact, the healthcare sector's critical nature amplifies the potential consequences. Disruption or data breaches in healthcare systems can affect patient care continuity and safety. European healthcare organizations must therefore prioritize addressing this vulnerability to maintain compliance and protect sensitive health information.

Summary

CVE-2025-9802 is a medium-severity SQL Injection vulnerability identified in RemoteClinic version 2.0, specifically within the /staff/profile.php file. The vulnerability arises from improper sanitization or validation of the 'ID' parameter, which an attacker can manipulate to inject malicious SQL code. This injection flaw allows an unauthenticated remote attacker with high privileges (PR:H) to execute arbitrary SQL commands against the backend database without requiring user interaction. The CVSS 4.0 vector indicates the attack is network exploitable (AV:N), requires no user interaction (UI:N), but does require high privileges, likely meaning the attacker must already have some level of authenticated access or elevated rights within the system. The impact on confidentiality, integrity, and availability is rated low, suggesting that while exploitation is possible, the scope or depth of damage is limited. No known exploits are currently reported in the wild, and no patches have been linked yet. The vulnerability could allow attackers to read, modify, or delete sensitive staff profile data, potentially leading to unauthorized data disclosure or corruption within the healthcare environment managed by RemoteClinic. Given the nature of healthcare data, even limited data integrity or confidentiality breaches can have serious consequences.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Sep 2025, 00:02 UTC

Technical details

References

Community reviews

Related threats