CVE-2025-43842
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, np7, trainset_dir4 and sr2 take user input and pass it to the preprocess_dataset 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. User-controlled parameters (exp_dir1, np7, trainset_dir4, sr2) are passed to the preprocess_dataset function and concatenated directly into a shell command without sanitization, 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<= 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 RVC WebUI installation directoryLocate the folder where Retrieval-based-Voice-Conversion-WebUI is installed. Common locations include /home/user/RVC, C:\RVC, or the current working directory if running from source.Affected if The installation directory cannot be found or the software is not installed.
-
Determine the installed versionCheck for a version file, look in the main Python files (such as infer-web.py, webui.py, or similar), or inspect the git repository if cloned. Look for version strings like '2.2.231006' or check the most recent git commit date.Affected if The version is 2.2.231006 or earlier, or the version cannot be determined but the software is present.
-
Locate the preprocess_dataset functionSearch the codebase for the string 'def preprocess_dataset' in Python files. This function is the entry point for the vulnerable parameters exp_dir1, np7, trainset_dir4, and sr2.Affected if The preprocess_dataset function exists in the codebase, indicating the vulnerable code path is present.
-
Verify command injection vulnerability in the functionExamine the preprocess_dataset function implementation. Look for direct use of os.system, subprocess.call, subprocess.run, or similar with string concatenation/templating involving the parameters exp_dir1, np7, trainset_dir4, or sr2.Affected if The function contains shell command execution using the user-controlled parameters without sanitization or parameterization.
-
Confirm web interface exposureDetermine if the web UI is running and accessible. Check for running processes listening on typical ports (7860, 8000, 5000) or inspect the application's route configuration for the preprocess_dataset endpoint.Affected if The web interface is running and exposes the preprocessing functionality to network users.
You are affected if the installed RVC WebUI version is 2.2.231006 or earlier AND the preprocess_dataset function uses shell command execution with the vulnerable parameters 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 · scopedImplement strict input validation and use parameterized execution methods or safe API calls instead of shell command concatenation. Avoid passing user input directly to system calls. Apply a patch when available.
- No patched version is currently available. Monitor the project's GitHub repository (github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI) for security updates.
- If immediate mitigation is required, consider deploying the application in a sandboxed environment with restricted network access and limited OS permissions.
- Review the preprocess_dataset function and implement input validation/sanitization on the exp_dir1, np7, trainset_dir4, and sr2 parameters to prevent command injection until an official patch is released.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43842 — 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-43842 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