CVE-2025-27774
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 · uneditedApplio 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 156 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 blind SSRF can also be coupled with the an arbitrary file read (e.g., CVE-2025-27784) to read files from hosts on the internal network, that the Applio server can reach, which would make it a full SSRF. 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 confidenceApplio versions 3.2.7 and prior contain a blind SSRF vulnerability in model_download.py (line 156) that allows attackers to send arbitrary HTTP requests from the server to internal network resources, and a file write vulnerability enabling arbitrary file creation on the server filesystem. These can be chained with other vulnerabilities like unsafe deserialization to achieve remote code 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<= 3.2.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Applio versionLocate the Applio installation directory and check the version file or metadata (often in version.py, __init__.py, or a package.json). If using a git repository, run 'git describe --tags' or check the release tag.Affected if Installed version is 3.2.7 or any earlier version (e.g., 3.2.6, 3.2.5, etc.)
-
Locate model_download.pySearch for the file model_download.py within the Applio source code directory structure, typically under the main application source folder.Affected if The file model_download.py exists in the Applio codebase
-
Inspect vulnerable code in model_download.pyOpen model_download.py and navigate to line 156 (or search for URL-fetching code, requests.get/post calls, or urllib operations). Verify if the code accepts user-controlled URLs without strict validation or allowlisting.Affected if Line 156 contains code that performs HTTP requests using unsanitized user input (e.g., direct use of user-supplied URLs in requests.get, urllib, or similar functions)
-
Determine if model download feature is exposedIdentify if the model download endpoint/function is exposed via an API route, web interface, or CLI. Check application routing files (e.g., routes.py, app.py) for endpoints that invoke the model download functionality.Affected if The model download feature is accessible (e.g., exposed via HTTP API or web endpoint without authentication or network restrictions)
-
Check for unsafe deserialization endpointsSearch the codebase for pickle.load, yaml.load (with unsafe loader), or similar deserialization functions that could be chained with the SSRF/file write vulnerabilities.Affected if Unsafe deserialization endpoints exist and are accessible, which could enable RCE when chained with the SSRF or file write flaws
A user is affected if they are running Applio version 3.2.7 or earlier AND the model_download.py file exists with the vulnerable code at line 156 AND the model download feature is exposed to untrusted input.
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 URL allowlisting and disable HTTP/s redirections in model_download.py to prevent SSRF. For the file write vulnerability, validate and sanitize all file paths, restrict write operations to a predefined safe directory, and remove any deserialization endpoints that could be chained for RCE.
- Isolate the Applio server on a restricted network segment to limit exposure to internal services
- Configure firewall rules to prevent the Applio server from making outbound connections to untrusted destinations
- Monitor network traffic for suspicious requests originating from the Applio server
- If possible, disable or restrict the model_download functionality until a patch is available
- Review and restrict file write permissions for the Applio service account
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27774 — 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-27774 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