CVE-2025-27776
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 240 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 arbitrary file read 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 240) that allows attackers to force the server to make requests to internal network resources or probe for additional vulnerabilities. The vulnerability also includes arbitrary file write capability that can be chained with other vulnerabilities like unsafe deserialization to achieve remote code execution. When combined with CVE-2025-27784 (arbitrary file read), the blind SSRF becomes a full SSRF enabling comprehensive internal network access.
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 installed Applio versionCheck the Applio application version number displayed in the web interface, or inspect version files in the Applio installation directory (such as version.py, __init__.py, or setup.py) to determine the exact version runningAffected if The 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 in the Applio installation directory and verify it exists at the expected path (typically under the main Applio source code structure)Affected if The file model_download.py exists and contains code around line 240 that handles URL fetching or model downloads
-
Inspect the vulnerable endpointExamine the model_download.py file, specifically around line 240, for code that takes user input (such as a URL parameter) and passes it to an HTTP request function without proper validationAffected if The code accepts URLs as input and makes outbound requests without validating that the target is not an internal network address (e.g., 127.0.0.1, 192.168.x.x, 10.x.x.x, or internal hostnames)
-
Check for arbitrary file write capabilityReview model_download.py for functions that write data to files based on user-controlled input, looking for patterns where filenames or file contents are derived from external input without sanitizationAffected if The code allows writing files to arbitrary locations on the filesystem based on user-supplied data
-
Look for signs of exploitationReview Applio server logs (access logs, error logs, and application logs) for suspicious outgoing HTTP requests to internal IP addresses (127.0.0.1, localhost, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or unusual file write operations to unexpected directoriesAffected if Logs show requests to internal network addresses or file writes to locations outside the intended models directory
You are affected if Applio version 3.2.7 or lower is running, the model_download.py file exists with the vulnerable URL-fetching logic at line 240, and the application accepts URL input without restricting internal network destinations.
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 network segmentation to restrict Applio server outbound connections, deploy WAF rules to detect and block SSRF payloads, and add strict input validation on model_download.py to prevent arbitrary file writes. Consider temporarily disabling the affected functionality until a patch is available.
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27776 — 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-27776 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