VulnerabilityPublished 19 Mar 2025Updated 2 Jul 2025

CVE-2025-26485: Beta80 Life 1st · Information Exposure

Affects Beta80 Life 1stSource CVE Database V5

Not known to be exploited · CVSS 5.8 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

5.8Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: 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: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 19 Mar 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 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
Beta80 Life 1st	Affected =1.5.2.14234	Fixed in–

AI-suggested

To mitigate this vulnerability effectively, European organizations should implement the following specific measures: 1) Standardize error messages for authentication failures to avoid revealing whether a username exists or not. This can be done by returning a generic error message such as 'Invalid username or password' regardless of the failure reason. 2) Implement rate limiting and account lockout policies to prevent automated enumeration attempts and brute force attacks. 3) Monitor authentication logs for unusual patterns indicative of enumeration or brute force activity and set up alerts for such anomalies. 4) Apply strict password policies and encourage multi-factor authentication (MFA) to reduce the risk of compromised credentials. 5) Engage with Beta80 for timely patches or updates addressing this vulnerability and plan for prompt deployment once available. 6) Conduct regular security assessments and penetration testing focusing on authentication mechanisms to identify similar information disclosure issues. 7) Educate users about phishing risks and suspicious login attempts, especially if user enumeration is suspected. These targeted actions go beyond generic advice by focusing on both technical controls and user awareness to reduce the attack surface and potential exploitation.

Description

A vulnerability in Beta80 Life 1st enables the retrieval of different error messages for failed authentication attempts (in case of the usage of a wrong password or a non existent user). The difference in the returned error messages could be used by attackers to understand whether a certain user is registered in the Identity Manager. This issue affects Life 1st: 1.5.2.14234.

Impact

For European organizations using Beta80 Life 1st version 1.5.2.14234, this vulnerability poses a risk primarily to the confidentiality of user identity information. Attackers can leverage the error message differences to enumerate valid users, which can lead to targeted brute force attacks or phishing campaigns aimed at those users. This can compromise user credentials or lead to unauthorized access if combined with other vulnerabilities or weak password policies. While the vulnerability does not directly affect system integrity or availability, the exposure of user information can undermine trust and compliance with data protection regulations such as the GDPR. Organizations in sectors with high identity management sensitivity, such as finance, healthcare, or government, may face increased risk due to the potential for targeted attacks. Additionally, the changed scope indicates that the impact may extend beyond the authentication component, possibly affecting other integrated systems relying on the Identity Manager. The absence of known exploits reduces immediate risk, but the ease of exploitation (no privileges or user interaction required) means attackers could quickly develop automated tools to exploit this flaw once discovered.

Summary

CVE-2025-26485 is a medium-severity vulnerability affecting Beta80's Life 1st product, version 1.5.2.14234. The flaw is categorized under CWE-200, which involves the exposure of sensitive information to unauthorized actors. Specifically, the vulnerability arises from the application's handling of authentication failures. When an attacker attempts to authenticate with either an incorrect password or a non-existent username, the system returns distinct error messages that differ based on the failure reason. This discrepancy allows an attacker to enumerate valid usernames registered in the Identity Manager component of Life 1st by analyzing the error responses. Such user enumeration can be a critical first step in targeted attacks, including brute force or social engineering campaigns. The CVSS v3.1 base score is 5.8, reflecting a medium severity level, with an attack vector of network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction needed (UI:N). The scope is changed (S:C), indicating that the vulnerability affects resources beyond the initially vulnerable component. The impact is limited to confidentiality (C:L), with no impact on integrity or availability. There are no known exploits in the wild at the time of publication, and no patches have been linked yet. The vulnerability was published on March 19, 2025, and was reserved on February 11, 2025, with ENISA as the assigner. Overall, this vulnerability enables attackers to gather sensitive information about user existence, which can facilitate further attacks against the system or its users.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (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
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (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

Affected software

Description

AI analysisMachine-generated, updated 2 Jul 2025, 14:39 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats