dbcve.org
ApplioApplication

CVE-2025-27786

CRITICAL · 9.1 CVSS v3.1 Published 2025-03-19
Fix available
A fix is available. Upgrade to after 3.2.8-bugfix or later.
See remediation →
100/100
Remediation priority · Urgent
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
Applio is a voice conversion tool. Versions 3.2.8-bugfix and prior are vulnerable to arbitrary file removal in core.py. `output_tts_path` in tts.py takes arbitrary user input and passes it to `run_tts_script` function in core.py, which checks if the path in `output_tts_path` exists, and if yes, removes that path, which leads to arbitrary file removal. As of time of publication, no known patches 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

Applio versions 3.2.8-bugfix and prior contain an arbitrary file removal vulnerability. User-controlled input from `output_tts_path` in tts.py is passed to the `run_tts_script` function in core.py, which checks if the path exists and removes it without proper validation, allowing attackers to delete arbitrary files on the system.

MitigationUntil an official patch is released, implement strict input validation on `output_tts_path` to restrict file operations to expected directories only, or apply file permission controls to limit the application's write/delete capabilities.

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
ApplioApplication
Affected:<= 3.2.8-bugfix

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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. Locate Applio installation and identify version
    Search for the Applio application directory, then check for version information in files like version.py, __init__.py, or a VERSION file within the Applio folder. Compare the found version against the affected range (<= 3.2.8-bugfix).
    Affected if Applio is installed and the version is 3.2.8-bugfix or any earlier version.
  2. Verify vulnerable source files exist
    Locate tts.py and core.py within the Applio installation directory. These files contain the vulnerable code path that processes the output_tts_path parameter.
    Affected if Both tts.py and core.py exist in the Applio installation, indicating the potentially vulnerable code is present.
  3. Confirm TTS functionality is accessible
    Determine if the TTS module is enabled and accessible in the Applio deployment. This could be via web API endpoint, CLI interface, or any exposed service that accepts the output_tts_path parameter.
    Affected if The TTS functionality is exposed through an API endpoint, web route, or CLI that accepts user-supplied output_tts_path input.
  4. Inspect run_tts_script for unsafe path handling
    Examine the run_tts_script function in core.py to confirm it performs file existence checks and deletion operations on the output_tts_path parameter without proper validation or sanitization.
    Affected if The run_tts_script function removes files based on the output_tts_path parameter without validating that the path is within an expected directory.

You are affected if Applio version 3.2.8-bugfix or earlier is installed, the vulnerable tts.py and core.py files are present, and the TTS functionality that accepts output_tts_path input is accessible in your deployment.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.2.8-bugfix
Interim mitigation

Until an official patch is released, implement strict input validation on `output_tts_path` to restrict file operations to expected directories only, or apply file permission controls to limit the application's write/delete capabilities.

Recommended fix High confidence
  1. Avoid using the TTS functionality in Applio until a security patch is released
  2. If TTS features are required, implement input validation on the `output_tts_path` parameter to ensure it only allows safe, expected file paths (e.g., restrict to a specific output directory and validate against path traversal attempts using path normalization and allowlist checks)
  3. Monitor the official Applio repository (github.com) for security updates addressing this vulnerability
  4. Consider implementing file permission restrictions to limit the impact of arbitrary file removal

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Applio Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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