CVE-2025-67728
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 · uneditedFireshare facilitates self-hosted media and link sharing. Versions 1.2.30 and below allow an authenticated user, or unauthenticated user if the Public Uploads setting is enabled, to craft a malicious filename when uploading a video file. The malicious filename is then concatenated directly into a shell command, which can be used for uploading files to arbitrary directories via path traversal, or executing system commands for Remote Code Execution (RCE). This issue is fixed in version 1.3.0.
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 confidenceFireshare versions 1.2.30 and below contain an OS command injection vulnerability in the video file upload functionality. User-supplied filenames are directly concatenated into shell commands without sanitization or escaping, enabling both path traversal (for arbitrary file writes) and remote code execution. Unauthenticated attackers can exploit this if Public Uploads is enabled; otherwise authenticated users can exploit it.
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< 1.3.0CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Fireshare versionCheck the installed version of Fireshare (typically via the web UI admin panel, or by checking the application binary/package version)Affected if Version is 1.2.30 or below, or any version lower than 1.3.0
-
Verify Public Uploads settingInspect the Fireshare configuration file or admin settings to determine if Public Uploads is enabled (look for a setting controlling unauthenticated file uploads)Affected if Public Uploads is enabled - this allows unauthenticated exploitation of the vulnerability
-
Confirm upload feature accessibilityDetermine whether the upload functionality is available to any authenticated users in the system (review user roles and permissions related to file uploads)Affected if Upload functionality is accessible to authenticated users - this allows authenticated exploitation when Public Uploads is disabled
-
Locate upload functionality logsReview application logs for any suspicious upload requests with unusual characters in filenames (such as semicolons, pipe symbols, backticks, or path traversal sequences like ../)Affected if Log entries show upload attempts with shell metacharacters in filenames, indicating possible exploitation attempts
A user is affected if Fireshare version is below 1.3.0 AND (Public Uploads is enabled OR any authenticated user has upload access).
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 · scoped1.3.0
Upgrade to Fireshare version 1.3.0 or later which includes proper input sanitization. Until patched, disable Public Uploads and restrict upload functionality to trusted authenticated users only.
version 1.3.0
- 1. Back up your existing Fireshare installation and database before upgrading
- 2. Upgrade Fireshare to version 1.3.0 or later using your deployment method (e.g., Docker pull, pip install, or git fetch)
- 3. Restart the Fireshare service to ensure the new version is running
- 4. Verify the upgrade was successful by checking the application version
- 5. Test that file uploads work correctly with normal filenames to confirm functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67728 — 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-67728 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