CVE-2024-8060
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 · uneditedOpenWebUI version 0.3.0 contains a vulnerability in the audio API endpoint `/audio/api/v1/transcriptions` that allows for arbitrary file upload. The application performs insufficient validation on the `file.content_type` and allows user-controlled filenames, leading to a path traversal vulnerability. This can be exploited by an authenticated user to overwrite critical files within the Docker container, potentially leading to remote code execution as the root user.
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 confidenceOpenWebUI 0.3.0 has an arbitrary file upload vulnerability in the `/audio/api/v1/transcriptions` endpoint. The application fails to properly validate the `file.content_type` and accepts user-controlled filenames, enabling path traversal that allows an authenticated attacker to overwrite critical files in the container, potentially achieving root-level RCE.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 OpenWebUI installation and versionCheck the running container or installed application version. For Docker: 'docker ps --format "{{.Names}} {{.Image}}" | grep -i openwebui' or check container labels/environment variables for version. For source installs: review the version file or git tag.Affected if The installed version is OpenWebUI 0.3.0 exactly, or falls within 0.3.0 to 0.3.x before patches.
-
Verify the transcriptions API endpoint is exposedCheck if the /audio/api/v1/transcriptions endpoint is accessible. Review reverse proxy configurations, firewall rules, or network policies that allow access to this endpoint from untrusted networks.Affected if The endpoint is reachable without additional network segmentation or authentication layers beyond the application login.
-
Confirm authentication configuration for the APIInspect the application's authentication settings. Check if the /audio/api/v1/transcriptions endpoint requires valid user credentials. Review session configuration and token validation for API routes.Affected if The endpoint accepts requests from any authenticated user, including low-privilege users, without additional authorization checks on file upload parameters.
-
Check container runtime configurationReview how the OpenWebUI container is running: 'docker inspect <container> | grep -i user' or check the container's user namespace configuration. Verify if the container runs as root (UID 0).Affected if The container runs as root user, making the path traversal attack more likely to succeed in overwriting system files.
-
Review file upload handling for the transcriptions featureExamine application logs or network traces when uploading a file to /audio/api/v1/transcriptions. Check if the server accepts arbitrary filenames or content-type values without validation.Affected if The application accepts user-supplied filenames and content-type headers without sanitization or rejection of path traversal sequences like '../'.
Your environment is affected if OpenWebUI version 0.3.0 is running, the /audio/api/v1/transcriptions endpoint is accessible to authenticated users, and the container runs with sufficient privileges to allow path traversal file writes.
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 dataImplement strict validation of file content types using magic-byte detection, sanitize filenames to prevent path traversal (e.g., reject ../ sequences, enforce whitelisted characters), and run the container as a non-root user to limit impact.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8060 — 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-2024-8060 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