dbcve.org
Gpt Sovits WebuiApplication · Rvc Boss

CVE-2025-49834

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

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
GPT-SoVITS-WebUI is a voice conversion and text-to-speech webUI. In versions 20250228v3 and prior, there is a command injection vulnerability in webui.py open_denoise function. denoise_inp_dir and denoise_opt_dir take user input, which is passed to the open_denoise function, which concatenates the user input into a command and runs it on the server, leading to arbitrary command execution. At time of publication, no known patched versions are available.

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

GPT-SoVITS-WebUI versions 20250228v3 and prior contain a command injection vulnerability in the open_denoise function within webui.py. The denoise_inp_dir and denoise_opt_dir parameters accept user-supplied input that is directly concatenated into a shell command without sanitization, allowing authenticated or remote attackers to execute arbitrary commands on the server with the privileges of the web application.

MitigationImplement input validation and use subprocess with argument lists (avoiding shell=True) to execute system commands, or refactor to use safer APIs that do not involve shell command execution. Consider deploying a WAF as an interim control until the code fix is implemented.

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
Gpt Sovits WebuiApplication
Affected:<= 20250228v3

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 GPT-SoVITS-WebUI installation
    Locate the webui.py file in the GPT-SoVITS-WebUI installation directory. Common paths include the project root or a 'GPT-SoVITS-WebUI' folder.
    Affected if The webui.py file exists and contains the open_denoise function definition.
  2. Check installed version
    Review the version metadata in the repository, setup.py, or version file. The affected version is labeled as 20250228v3 or earlier.
    Affected if The installed version is 20250228v3 or any version prior to it.
  3. Verify vulnerable code exists in webui.py
    Open webui.py and search for the open_denoise function. Inspect how denoise_inp_dir and denoise_opt_dir parameters are used in shell command construction.
    Affected if The function uses string concatenation to build shell commands with user-supplied directory paths without subprocess.run(shell=False) or input sanitization.
  4. Confirm denoise feature is accessible
    Check if the web UI exposes the denoise functionality through an API endpoint, button, or parameter that accepts directory input.
    Affected if The denoise feature is enabled and accepts user-controlled directory path input.
  5. Check web application execution context
    Identify the user account and permissions under which the web application runs (e.g., process owner, service account).
    Affected if The web application runs with elevated privileges or has access to sensitive system resources.

You are affected if GPT-SoVITS-WebUI version 20250228v3 or earlier is installed, the open_denoise function uses unsanitized string concatenation for shell commands, and the denoise feature accepts user-supplied directory paths.

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.

From vendor data
Upgrade available Upgrade to a release after 20250228v3
Interim mitigation

Implement input validation and use subprocess with argument lists (avoiding shell=True) to execute system commands, or refactor to use safer APIs that do not involve shell command execution. Consider deploying a WAF as an interim control until the code fix is implemented.

Fix this in Gpt Sovits Webui Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49834 — 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-49834 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