CVE-2025-43844
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 · uneditedRetrieval-based-Voice-Conversion-WebUI is a voice changing framework based on VITS. Versions 2.2.231006 and prior are vulnerable to command injection. The variables exp_dir1, among others, take user input and pass it to the click_train function, which concatenates them into a command that is run on the server. This can lead to arbitrary command execution. As of time of publication, no known patches exist.
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 confidenceRetrieval-based-Voice-Conversion-WebUI versions 2.2.231006 and prior contain a command injection vulnerability where user-controlled input (including exp_dir1) is concatenated directly into shell commands via the click_train function. An attacker can inject arbitrary OS commands by providing specially crafted input parameters, achieving unauthenticated remote code execution with critical severity.
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<= 2.2.231006CVSS 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 the installed RVC WebUI versionLocate the version file or check the source code for version information, typically found in the main application directory or a version config fileAffected if The version is 2.2.231006 or any version prior to it (e.g., 2.2.x, 2.1.x, earlier releases)
-
Verify the click_train function exists in the codebaseSearch the source code for the click_train function definition, particularly in files handling the training moduleAffected if The click_train function is present and processes user-supplied parameters including exp_dir1
-
Determine if the web interface is network-accessibleCheck if the RVC WebUI application is running and exposed on a network-accessible interface (e.g., listening on 0.0.0.0 or external IP rather than localhost only)Affected if The web interface is accessible from untrusted networks without proper network isolation
-
Inspect the click_train function for unsafe command constructionExamine the click_train function source code for direct string concatenation of user inputs (particularly exp_dir1) into shell commands, look for patterns like subprocess calls with shell=True using f-strings or string formatting with user variablesAffected if The code uses string concatenation or formatting to build shell commands from user inputs without sanitization or parameterized execution
You are affected if you are running RVC WebUI version 2.2.231006 or earlier, the web interface is network-accessible, and the click_train function contains direct shell command construction from user input without proper 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 · scopedImplement strict input validation and use parameterized command execution methods (e.g., subprocess with argument lists instead of shell=True, or shell escaping functions) for all user-supplied parameters before passing them to click_train. Network isolation and least-privilege service accounts provide additional defense-in-depth until a patch is available.
- Do not expose this application to untrusted networks or the internet until a security patch is released
- If the application must be used, implement network-level segmentation and strict firewall rules to limit access to trusted IP addresses only
- Monitor the official GitHub repository (github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI) for security updates and patches
- Consider disabling or restricting the click_train function and any related endpoints that accept user input for exp_dir1 and similar parameters until a fix is available
- Implement input validation and sanitization at a reverse proxy or WAF level as a temporary compensating control
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43844 — 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-43844 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