dbcve.org
3x UiApplication · Mhsanaei

CVE-2025-29331

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-26
Fix available
A fix is available. Upgrade to 2.5.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The x-ui management script in MHSanaei 3x-ui versions before v2.5.3 disables certificate verification when using wget to download updates, allowing a remote attacker performing a man-in-the-middle attack to inject and execute arbitrary code by serving malicious update packages.

MitigationUpgrade to MHSanaei 3x-ui v2.5.3 or later, which properly validates certificates during update downloads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
3x UiApplication
Affected:< 2.5.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if MHSanaei 3x-ui is installed
    Look for the x-ui binary or script on the system, typically in /usr/local/bin/x-ui or /usr/bin/x-ui, or check for the 3x-ui package in the system's package manager
    Affected if The x-ui binary or management script is found on the system
  2. Determine the installed version of x-ui
    Run the x-ui version command, or check the version file if one exists in the installation directory (commonly /usr/local/x-ui or the config directory)
    Affected if The version number is lower than 2.5.3 (e.g., 2.5.2, 2.5.1, 2.0.x, etc.)
  3. Inspect the update mechanism in the x-ui script
    Examine the x-ui script file for functions that handle updates; look for wget commands that download from remote URLs
    Affected if The script contains wget commands used for downloading updates or packages
  4. Check if certificate verification is disabled in wget calls
    Search within the x-ui script for wget commands with options like --no-check-certificate, -no-check-certificate, or --insecure that disable SSL/TLS certificate validation
    Affected if The wget command used for updates includes options that disable certificate verification (such as --no-check-certificate)
  5. Determine if the update feature is configured or enabled
    Check if the system's update functionality is actively used or if automatic updates are enabled in the x-ui configuration
    Affected if The system uses the x-ui update mechanism to fetch updates from remote servers

A system is affected if it runs MHSanaei 3x-ui with a version lower than 2.5.3 AND uses the built-in update mechanism that employs wget with disabled certificate verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.5.3 or later
Fixed in 2.5.3
Vendor patch github.com →
Interim mitigation

Upgrade to MHSanaei 3x-ui v2.5.3 or later, which properly validates certificates during update downloads.

Recommended fix High confidence

version 2.5.3

  1. 1. Back up the current 3x-ui configuration and data directory to prevent data loss
  2. 2. Upgrade to version 2.5.3 or later by pulling the latest version from the official repository
  3. 3. Verify that wget is now properly validating certificates during update downloads
  4. 4. Confirm the upgrade was successful by checking the version number in the UI or via command line

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 3x Ui Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29331 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29331 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data