CVE-2025-29331
Published: 26 June 2025
Summary
CVE-2025-29331 is a critical-severity Improper Certificate Validation (CWE-295) vulnerability in Mhsanaei 3X-Ui. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 16.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
CVE-2025-29331 is an improper certificate validation flaw (CWE-295) in the MHSanaei 3x-ui management panel prior to version 2.5.3. The x-ui update script invokes wget with the --no-check-certificate flag when retrieving new releases, allowing an attacker to supply a malicious update package over an untrusted channel without triggering certificate errors.
A remote attacker with no credentials or user interaction can exploit the weakness by serving a crafted update payload from a network position that intercepts or redirects the download. Successful exploitation grants arbitrary code execution with the privileges of the x-ui process, resulting in full confidentiality, integrity, and availability impact as reflected in the CVSS 9.8 score.
The referenced GitHub pull request 2661 and the Digilol security advisory DLSEC2025-001 describe the corrective change that removes the insecure wget flag and enforces proper certificate validation; administrators are advised to upgrade to 2.5.3 or later. The associated EPSS score has remained flat at 0.0190 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-19195
Vulnerability details
An issue in MHSanaei 3x-ui before v.2.5.3 and before allows a remote attacker to execute arbitrary code via the management script x-ui passes the no check certificate option to wget when downloading updates
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
When certificates are used to establish component provenance, the control requires correct certificate validation procedures.
Mandates approved trust anchors and issuance policies, directly preventing acceptance of unvalidated or untrusted certificates.
Correct system time is required for proper enforcement of certificate notBefore/notAfter dates and time-based revocation checks.