CVE-2025-43843
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 and f0method8 take user input and pass it into the extract_f0_feature 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 in the extract_f0_feature function. User-controlled variables exp_dir1, np7, and f0method8 are concatenated directly into a shell command without sanitization, allowing arbitrary OS command execution.
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 installed RVC WebUI versionCheck the version file or about page in the RVC WebUI interface, or look for version metadata in the installation directory. Common locations include a version.py file, setup.py, or the main application files.Affected if The installed version is 2.2.231006 or any version prior to it.
-
Locate the extract_f0_feature functionSearch the source code for the function named 'extract_f0_feature' - this is typically found in inference/voice_change.py or similar processing modules within the RVC installation directory.Affected if The function exists in the codebase and contains direct string concatenation of variables into shell commands.
-
Verify vulnerable parameter usageExamine the extract_f0_feature function code and look for usage of variables exp_dir1, np7, and f0method8 being concatenated into shell commands using f-strings, format(), or + operator without sanitization.Affected if The code shows exp_dir1, np7, or f0method8 being passed directly to shell execution functions (such as os.system, subprocess.call with shell=True) without input validation.
-
Check web interface exposureDetermine if the RVC WebUI HTTP server is accessible over the network. Review the startup command or configuration for the --port and --share flags, and check firewall rules.Affected if The web interface is exposed to untrusted networks, allowing remote attackers to supply malicious parameter values.
-
Confirm input validation absenceSearch the codebase for input validation or sanitization functions applied to exp_dir1, np7, and f0method8 before shell execution. Look for patterns like shlex.quote, input sanitization functions, or parameterized command execution.Affected if No input validation or sanitization is performed on these variables before they are used in shell commands.
You are affected if you have RVC WebUI version 2.2.231006 or earlier installed AND the extract_f0_feature function uses exp_dir1, np7, or f0method8 in unsanitized shell commands accessible to untrusted users.
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.
From vendor dataSince no official patch exists, implement strict input validation and sanitize all user-provided variables before use in system calls. Preferably, refactor to use parameterized command execution methods instead of shell string concatenation. Restrict network access to the service until fixed.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43843 — 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-43843 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