CVE-2025-67719: ibexa user · Unverified Password Change
Affects ibexa userSource CVE Database V5
Not known to be exploited · CVSS 8.5 High · fixed in 5.0.4 : patch ibexa user soon.
Data as of 25 Oct 2026, 19:02 UTC
- 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.
- Patch
- Available – fixed in 5.0.4
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Dec 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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubibexa/userpkg:github/ibexa/userOther threats | Affected– | Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
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.
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.
References
- github.com/ibexa/user/security/advisories/GHSA-x93p-w2ch-fg67 (opens in a new tab)
- github.com/ibexa/user/commit/9d485bf385e6401c9f7ee80287d8ccd00f73dcf4 (opens in a new tab)
- developers.ibexa.co/security-advisories/ibexa-sa-2025-005-password-change-and-xss-vulnerabilities-in-back-office (opens in a new tab)