CVE-2025-49835
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 · uneditedGPT-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_asr function. asr_inp_dir (and a number of other variables) takes user input, which is passed to the open_asr 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 confidenceGPT-SoVITS-WebUI versions 20250228v3 and prior contain a command injection vulnerability in the open_asr function in webui.py. The asr_inp_dir parameter (and potentially other variables) accepts user input that gets concatenated directly into a shell command, allowing arbitrary command execution on the server.
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<= 20250228v3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify GPT-SoVITS-WebUI installation locationSearch for webui.py file in common locations such as the current working directory, /opt/GPT-SoVITS/, or ~/GPT-SoVITS/. Use 'find / -name webui.py 2>/dev/null' to locate all instances.Affected if The webui.py file from GPT-SoVITS is found on the system
-
Determine installed versionCheck the version file or git log in the GPT-SoVITS installation directory. Common locations: version file, git tag, or README.md. Look for version strings like '20250228v3' or later.Affected if The installed version is 20250228v3 or any version prior to this
-
Verify vulnerable function existsOpen webui.py and search for the 'open_asr' function definition. Look for lines where 'asr_inp_dir' parameter is used in command construction, typically involving os.system, subprocess with shell=True, or string concatenation into shell commands.Affected if The open_asr function exists and directly concatenates asr_inp_dir into shell commands without sanitization
-
Check network exposure of the WebUIReview the webui.py startup configuration or any --host/--port flags. Look for binding to '0.0.0.0' instead of '127.0.0.1', or check if the service is listening on a public IP using 'netstat -tlnp' or 'ss -tlnp'.Affected if The WebUI is bound to 0.0.0.0 or a public IP address and is accessible over the network
-
Inspect input handling for asr_inp_dirIn webui.py, examine how the asr_inp_dir parameter is processed before being used in shell commands. Check if there is any input validation, sanitization, or use of subprocess with shell=False and argument lists.Affected if asr_inp_dir is passed directly to shell execution functions without validation or sanitization, or shell=True is used with string formatting
The environment is affected if GPT-SoVITS-WebUI version 20250228v3 or earlier is installed and the open_asr function directly uses the asr_inp_dir parameter in shell commands without input sanitization.
Generated from the published advisory. Verify against your own configuration.
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 · scopedSince no patched version is available, immediately restrict network access to the webUI, implement strict input validation/sanitization on all user-supplied parameters before command construction, and replace shell command execution with safer alternatives such as subprocess with shell=False and argument lists.
- Isolate the affected system from untrusted networks since no patch is available.
- If exposure to untrusted users is not required, run the application in a local-only mode or behind a properly configured firewall.
- Review and implement input validation on all user-supplied parameters, particularly asr_inp_dir and related variables, before they are used in any system calls.
- Run the application with the minimum privileges necessary to reduce the impact of potential command injection.
- Monitor for any suspicious command execution or unexpected system behavior.
- Check the project repository at github.com for updated releases that may address this vulnerability in the future.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49835 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49835 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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