VulnerabilityPublished 25 Jun 2025Updated 28 Jun 2025

CVE-2025-6664: CodeAstro Patient Record Management System · Cross-Site Request Forgery

Affects CodeAstro Patient Record Management SystemSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 25 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, 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 or the CVSS exploit maturity 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
CodeAstro Patient Record Management System	Affected =1.0	Fixed in–

AI-suggested

Implement strict CSRF protections at the application level, such as synchronizer tokens or double-submit cookies, to validate the origin of requests.
Employ web application firewalls (WAFs) with rules specifically designed to detect and block CSRF attack patterns targeting the Patient Record Management System.
Conduct user awareness training focused on phishing and social engineering to reduce the likelihood of users interacting with malicious content that could trigger CSRF attacks.
Restrict access to the Patient Record Management System to trusted networks or VPNs to reduce exposure to external threats.
Monitor application logs for unusual or unauthorized actions that could indicate exploitation attempts.
Segregate duties and enforce least privilege principles within the system to limit the impact of unauthorized actions.
Engage with the vendor (CodeAstro) for timely updates and patches, and prepare to apply them promptly once available.
Consider implementing Content Security Policy (CSP) headers to reduce the risk of malicious script execution that could facilitate CSRF attacks.
Use multi-factor authentication (MFA) where possible to add an additional layer of security, although it does not directly prevent CSRF, it can reduce overall risk.

Description

A vulnerability, which was classified as problematic, was found in CodeAstro Patient Record Management System 1.0. Affected is an unknown function. The manipulation leads to cross-site request forgery. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European healthcare organizations using CodeAstro Patient Record Management System 1.0, this vulnerability poses a significant risk to the integrity of patient data and the reliability of healthcare operations. Unauthorized actions triggered via CSRF could result in altered patient records, mismanagement of treatment plans, or unauthorized disclosure of sensitive health information if combined with other vulnerabilities. Although the confidentiality impact is rated low, the integrity impact is more concerning in a healthcare context where data accuracy is critical. Disruption or manipulation of patient records could lead to medical errors, regulatory non-compliance (e.g., GDPR violations), and reputational damage. The remote and unauthenticated nature of the attack vector means that attackers can target healthcare staff through phishing or malicious websites, increasing the attack surface. European healthcare providers are particularly sensitive to such threats due to strict data protection regulations and the critical nature of healthcare services. The lack of available patches means organizations must rely on compensating controls until a fix is released.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Jun 2025, 20:56 UTC

Technical details

References

Community reviews

Related threats