ibexa user up to 5.0.3 unverified password change

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.1$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in ibexa user up to 5.0.3. The affected element is an unknown function. This manipulation causes unverified password change. This vulnerability appears as CVE-2025-67719. The attack requires local access. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability has been found in ibexa user up to 5.0.3 and classified as problematic. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a unverified password change vulnerability. The CWE definition for the vulnerability is CWE-620. When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2025-67719 since 12/10/2025. The exploitation appears to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.

Upgrading to version 5.0.4 eliminates this vulnerability. Applying the patch 9d485bf385e6401c9f7ee80287d8ccd00f73dcf4 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202512-2248). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Unverified password change
CWE: CWE-620 / CWE-640
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: user 5.0.4
Patch: 9d485bf385e6401c9f7ee80287d8ccd00f73dcf4

Timelineinfo

12/10/2025 CVE reserved
12/11/2025 +1 days Advisory disclosed
12/11/2025 +0 days VulDB entry created
12/14/2025 +3 days VulDB entry last update

Sourcesinfo

Product: github.com

Advisory: GHSA-x93p-w2ch-fg67
Status: Confirmed

CVE: CVE-2025-67719 (🔒)
GCVE (CVE): GCVE-0-2025-67719
GCVE (VulDB): GCVE-100-335803
CNNVD: CNNVD-202512-2248 - Ibexa User Bundle 安全漏洞

Entryinfo

Created: 12/11/2025 07:24
Updated: 12/14/2025 16:46
Changes: 12/11/2025 07:24 (68), 12/12/2025 15:48 (6), 12/13/2025 23:04 (1), 12/14/2025 16:46 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!