CVE-2025-6452VulnerabilityPublished 22 Jun 2025Updated 24 Jun 2025

CVE-2025-6452: CodeAstro Patient Record Management System · Cross Site Scripting

Affects CodeAstro Patient Record Management SystemSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

4.8Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% 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:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

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

Threat metrics

Exploit Maturity: POC

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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Jun 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 2026-10-26.

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
GitHubvanshdhawan188/CodeAstro-Online-Healthcare-Patient-Record-Management-System`pkg:github/vanshdhawan188/CodeAstro-Online-Healthcare-Patient-Record-Management-System`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate application of input validation and output encoding on the 'Patient Name/Name' parameter within the 'Generate New Report' page to neutralize malicious scripts. 2. Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser context. 3. Conduct a thorough security review of all user input handling across the Patient Record Management System to identify and remediate similar XSS vectors. 4. Deploy Web Application Firewalls (WAF) with rules tailored to detect and block XSS payloads targeting the affected endpoint. 5. Educate healthcare staff on recognizing phishing attempts and suspicious behaviors that may result from XSS exploitation. 6. Monitor application logs and user activity for anomalies that could indicate exploitation attempts. 7. Coordinate with CodeAstro for official patches or updates; if unavailable, consider temporary mitigations such as disabling the vulnerable feature or restricting access to trusted users only. 8. Regularly update browsers and endpoint security solutions to reduce the impact of client-side attacks.

Description

A vulnerability was found in CodeAstro Patient Record Management System 1.0. It has been rated as problematic. This issue affects some unknown processing of the component Generate New Report Page. The manipulation of the argument Patient Name/Name leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations, particularly healthcare providers using CodeAstro Patient Record Management System 1.0, this vulnerability poses a risk of client-side attacks that can compromise user sessions and lead to unauthorized access to patient data or manipulation of records. Although the vulnerability itself does not directly allow data exfiltration or system compromise, the execution of malicious scripts in users' browsers can facilitate phishing, credential theft, or unauthorized actions within the application. This can undermine patient confidentiality and trust, potentially violating GDPR regulations concerning personal health data protection. Additionally, exploitation could disrupt healthcare workflows, impacting service availability indirectly. The medium severity rating suggests that while the risk is not critical, the sensitive nature of healthcare data and regulatory environment in Europe elevates the potential consequences of exploitation. Organizations may face reputational damage, regulatory fines, and operational disruptions if this vulnerability is exploited.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Jun 2025, 03:04 UTC

Technical details

References

Community reviews

Related threats