CVE-2025-35031VulnerabilityPublished 29 Sep 2025

CVE-2025-35031: Medical Informatics Engineering Enterprise Health · Debug Messages Revealing Unnecessary Information

Affects Medical Informatics Engineering Enterprise HealthSource CVE Database V5

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

3.3Low

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

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 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 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

AI-suggested

European healthcare organizations should immediately update Medical Informatics Engineering Enterprise Health to versions released after 2025-04-08 that contain the fix for CVE-2025-35031. Until updates are applied, organizations should restrict access to debug output logs and ensure that debug mode is disabled in production environments to prevent inadvertent exposure of session tokens. User training is critical to reduce the risk of social engineering attacks that might trick users into sharing debug information. Implement monitoring to detect unusual session activities that could indicate token misuse. Additionally, enforce strict session management policies, such as short session lifetimes and token invalidation upon logout, to minimize the window of opportunity for attackers. Regular security audits should verify that debug information does not leak sensitive data. Finally, consider network segmentation and access controls to limit who can access diagnostic outputs.

Description

Medical Informatics Engineering Enterprise Health includes the user's current session token in debug output. An attacker could convince a user to send this output to the attacker, thus allowing the attacker to impersonate that user. This issue is fixed as of 2025-04-08.

Impact

For European organizations, particularly those in the healthcare sector using Medical Informatics Engineering's Enterprise Health software, this vulnerability poses a risk of session hijacking through social engineering. If an attacker convinces a user to share debug output containing session tokens, the attacker can impersonate that user, potentially accessing sensitive patient data or performing unauthorized actions. Although the vulnerability does not directly compromise system integrity or availability, the confidentiality breach could lead to privacy violations and regulatory non-compliance under GDPR. The impact is somewhat limited by the requirement for user interaction and local access to debug output, reducing the likelihood of widespread exploitation. However, healthcare organizations are high-value targets due to the sensitivity of medical data, so even low-severity vulnerabilities warrant prompt attention. The lack of known exploits reduces immediate risk but does not eliminate the potential for targeted attacks, especially via phishing or insider threats.

CWE-1295Debug Messages Revealing Unnecessary Information (opens in a new tab)
Base weakness
The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.
Implementation
Ensure that a debug message does not reveal any unnecessary information during the debug process for the intended response.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Exploit Non-Production Interfaces (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 7 Oct 2025, 00:44 UTC

WeaknessesCWE-1295

Technical details

References

Community reviews

Related threats