VulnerabilityPublished 8 Jan 2026

CVE-2025-8307: Asseco InfoMedica Plus · Storing Passwords in a Recoverable Format

Affects Asseco InfoMedica PlusSource CVE Database V5

Not known to be exploited · CVSS 5.9 Medium : upgrade to 5.38.0 or 4.50.1 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

5.9Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.38.0, 4.50.1

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

Attack Vector: Local
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
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: Local: The vulnerable system 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 through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
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: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within 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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jan 2026
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 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

Upgrade Asseco InfoMedica Plus to 5.38.0 or 4.50.1.

Affected software

Product	Affected	Fixed in
AssecoInfoMedica Plus	Affected >=5.0.0 <5.38.0	Fixed in 5.38.0
AssecoInfoMedica Plus	Affected >=4.0.0 <4.50.1	Fixed in 4.50.1

AI-suggested

Upgrade Asseco InfoMedica Plus to versions 4.50.1 or 5.38.0 or later, where the vulnerability has been fixed.
Restrict access to databases and backup files containing encoded passwords using strict access control policies and network segmentation.
Implement monitoring and auditing of database access to detect unauthorized attempts to retrieve encoded passwords.
Educate staff about the risks of insider threats and enforce the principle of least privilege for database and system access.
Consider additional encryption or tokenization of sensitive data at rest to reduce exposure in case of database compromise.
Review and enhance incident response plans to quickly address potential credential compromise scenarios.
If upgrading immediately is not feasible, isolate affected systems from untrusted networks and limit client-side software distribution to trusted users only.
Regularly verify that no encoded password dumps or backups have been leaked or exposed externally.

Description

Asseco InfoMedica is a comprehensive solution used to manage both administrative and medical tasks in the healthcare sector. Passwords of all users are stored in a database in an encoded format. An attacker in possession of these encoded passwords is able to decode them by using an algorithm embedded in the client-side part of the software. This vulnerability has been fixed in versions 4.50.1 and 5.38.0

Impact

For European healthcare organizations using Asseco InfoMedica Plus versions 4.0.0 or 5.0.0, this vulnerability could lead to unauthorized disclosure of user credentials. Compromise of passwords may enable attackers to access sensitive patient data, alter administrative records, or disrupt healthcare operations. Given the sensitive nature of healthcare data, breaches could result in violations of GDPR and other data protection regulations, leading to legal and financial penalties. The impact is heightened in environments where database access controls are weak or where backups are insufficiently protected. Although exploitation requires local access to encoded passwords, insider threats or attackers who gain initial footholds could leverage this vulnerability to escalate privileges or move laterally within healthcare networks. The medium severity rating reflects the balance between the difficulty of exploitation and the sensitivity of the data at risk. Overall, this vulnerability undermines trust in the confidentiality of healthcare information systems and could have serious operational and reputational consequences for affected organizations.

CWE-257Storing Passwords in a Recoverable Format (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2021: Insecure Design (opens in a new tab)
The storage of passwords in a recoverable format makes them subject to password reuse attacks by malicious users. In fact, it should be noted that recoverable encrypted passwords provide no significant benefit over plaintext passwords since they are subject not only to reuse by malicious attackers but also by malicious insiders. If a system administrator can recover a password directly, or use a brute force search on the available information, the administrator can use the password on other accounts.
Architecture and Design
Use strong, non-reversible encryption to protect stored passwords.
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Password Brute Forcing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cert.pl/en/posts/2026/01/CVE-2025-8306/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jan 2026, 14:20 UTC

WeaknessesCWE-257

Technical details

References

Community reviews

Related threats