dbcve.org
ApplioApplication

CVE-2025-27775

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-19
Fix available
A fix is available. Upgrade to after 3.2.7 or later.
See remediation →
62/100
Remediation priority · Elevated
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.7 and prior are vulnerable to server-side request forgery (SSRF) and file write in `model_download.py` (line 143 in 3.2.7). The blind SSRF allows for sending requests on behalf of Applio server and can be leveraged to probe for other vulnerabilities on the server itself or on other back-end systems on the internal network, that the Applio server can reach. The file write allows for writing files on the server, which can be coupled with other vulnerabilities, for example an unsafe deserialization, to achieve remote code execution on the Applio server. 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.7 and prior contain a blind SSRF vulnerability and arbitrary file write in model_download.py (line 143). The SSRF allows the server to be leveraged as a proxy to probe internal network services, while the file write capability can be chained with other vulnerabilities like unsafe deserialization to achieve remote code execution.

MitigationSince no patch is available, disable or restrict the model_download functionality, implement strict URL allowlist validation and file path sanitization, and network-segment the Applio server to limit internal service exposure.

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.7

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Check installed Applio version
    Locate the version file or check the main Applio application metadata (often in version.py, __init__.py, setup.py, or a config file in the Applio installation directory). Run 'grep -r "version"' or 'cat version' in the Applio root directory.
    Affected if Version is 3.2.7 or any version lower than 3.2.7 (e.g., 3.2.6, 3.2.5, 3.0.0)
  2. Verify model_download.py exists
    Locate the model_download.py file in the Applio installation. Search using 'find /path/to/applio -name model_download.py' or check the typical source code structure.
    Affected if The file model_download.py exists in the Applio codebase, particularly if it contains a download function near line 143
  3. Check if model_download functionality is enabled
    Inspect Applio's configuration files (e.g., config.py, settings.py, app.py) or examine the model_download.py code to determine if the download feature is actively loaded or exposed as an API endpoint.
    Affected if The model_download module is imported, loaded, or exposed as a web route/endpoint in the running application
  4. Assess network exposure of the download feature
    Review the application's routing or API definitions to determine if model_download endpoints are accessible over the network. Check for any authentication or network restrictions on these endpoints.
    Affected if The model_download endpoint is reachable remotely without authentication or additional network filtering

You are affected if your Applio version is 3.2.7 or earlier AND the model_download.py module is present and accessible in your running application.

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.7
Interim mitigation

Since no patch is available, disable or restrict the model_download functionality, implement strict URL allowlist validation and file path sanitization, and network-segment the Applio server to limit internal service exposure.

Recommended fix Low confidence
  1. No official patch or fixed version is available for this vulnerability as of the advisory publication date.
  2. Monitor the official Applio repository (github.com/idosal/Applio) for future security updates.
  3. Implement network segmentation to restrict the Applio server's ability to make outbound connections to internal resources.
  4. Consider placing the application behind a WAF configured to detect and block SSRF patterns.
  5. Restrict file system permissions to limit the impact of arbitrary file write vulnerabilities.

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-27775 — 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-27775 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