Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-67719: CWE-620: Unverified Password Change in ibexa user

0
High
VulnerabilityCVE-2025-67719cvecve-2025-67719cwe-620
Published: Thu Dec 11 2025 (12/11/2025, 01:16:15 UTC)
Source: CVE Database V5
Vendor/Project: ibexa
Product: user

Description

Ibexa is a composable end-to-end DXP (Digital Experience Platform). Versions 5.0.0-beta1 through 5.0.3 do not have password validation. During the transition from v4 to v5 an error was introduced into validation code which causes the validation of the previous password not to run as expected. This makes it possible for a logged in user to change their password in the back office without knowing the previous password. For example, if a user logs into their account and walks away without locking their workstation, an attacker could access the unattended session and change the password, therefore locking the legitimate user out. This issue is fixed in version 5.0.4.

AI-Powered Analysis

AILast updated: 12/18/2025, 05:01:22 UTC

Technical Analysis

CVE-2025-67719 is a vulnerability classified under CWE-620 (Unverified Password Change) affecting Ibexa's Digital Experience Platform (DXP) user management component. Specifically, versions from 5.0.0-beta1 up to but not including 5.0.4 contain a logic error introduced during the transition from version 4 to 5, which disables the validation of the current password when a user attempts to change their password in the back office interface. This flaw means that any authenticated user can change their own password without knowing the existing password, effectively bypassing a critical security control. The vulnerability arises because the password validation routine fails to execute as intended, allowing password changes without verification. Exploitation requires the attacker to have access to an active user session, which could occur if a user leaves their workstation unlocked or if session hijacking is possible. The impact includes potential account lockout of legitimate users and unauthorized account control, threatening confidentiality and availability. The vulnerability has a CVSS 4.0 score of 8.5 (high severity), reflecting its serious impact and relatively low attack complexity, though it requires local access to an authenticated session. The issue is resolved in Ibexa version 5.0.4, which restores proper password validation. No public exploits have been reported to date.

Potential Impact

For European organizations using Ibexa DXP versions 5.0.0-beta1 through 5.0.3, this vulnerability poses a significant risk to user account security and operational continuity. Attackers with access to an unattended or hijacked session can change passwords without knowing the original credentials, potentially locking out legitimate users and disrupting business processes reliant on the platform. This can lead to denial of service for affected accounts and may facilitate further unauthorized access if attackers leverage the compromised accounts. Confidentiality is at risk as attackers gain control over user identities, and availability is impacted by account lockouts. Given that Ibexa is used in digital experience and content management scenarios, exploitation could affect customer-facing services, internal workflows, and sensitive data management. The vulnerability's requirement for an active session limits remote exploitation but elevates risk in environments with weak session management or physical security. The lack of known exploits suggests limited current threat activity, but the high severity score warrants urgent remediation to prevent potential abuse.

Mitigation Recommendations

European organizations should immediately upgrade Ibexa DXP installations to version 5.0.4 or later, where the password validation issue is fixed. Until patching is complete, organizations should enforce strict session management policies, including automatic session timeouts, screen locking on inactivity, and user training to prevent leaving sessions unattended. Implementing multi-factor authentication (MFA) can reduce the risk of session hijacking. Monitoring and alerting on unusual password change activities can help detect exploitation attempts. Network segmentation and access controls should limit who can reach the back office interface. Additionally, organizations should review audit logs for suspicious password changes and consider temporary restrictions on password changes for sensitive accounts. Regular vulnerability scanning and penetration testing focused on session management and authentication controls will help identify residual risks. Finally, ensure that all users are informed about the importance of locking their workstations when away to mitigate local exploitation vectors.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-10T18:46:14.762Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 693a262ebbbecd30a6f23ccd

Added to database: 12/11/2025, 2:02:22 AM

Last enriched: 12/18/2025, 5:01:22 AM

Last updated: 2/7/2026, 11:04:13 AM

Views: 98

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats