CVE-2025-13949
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 · uneditedA vulnerability was identified in ProudMuBai GoFilm 1.0.0/1.0.1. Impacted is the function SingleUpload of the file /server/controller/FileController.go. The manipulation of the argument File leads to unrestricted upload. The attack may be initiated remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceUnrestricted file upload vulnerability in the SingleUpload function of FileController.go in ProudMuBai GoFilm versions 1.0.0 and 1.0.1. An attacker can upload arbitrary files to the server without proper validation of file type, content, or extension, potentially leading to remote code execution if uploaded files are accessible and executable.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 GoFilm installation versionLocate the GoFilm application binary or source code and check its version identifier. Common locations: the binary name, a version file, or the main executable's metadata.Affected if Version is 1.0.0 or 1.0.1
-
Locate FileController.go source fileSearch the application source tree for FileController.go containing the SingleUpload function. Inspect the function code to confirm it lacks file type, content, or extension validation.Affected if SingleUpload function exists and contains no file validation logic
-
Verify upload endpoint is exposedCheck the application's routing configuration to confirm the file upload endpoint (typically /upload or similar) is accessible without authentication or with weak auth.Affected if Upload endpoint is publicly accessible or accessible to untrusted users
-
Inspect web server upload configurationReview the web server configuration (nginx, Apache, or embedded) handling file upload requests. Check if it enforces any Content-Type or extension restrictions.Affected if Web server applies no additional upload restrictions beyond the application
-
Check uploaded file storage locationIdentify where uploaded files are stored. Inspect configuration to determine if files are stored within or outside the web root.Affected if Uploaded files are stored inside the web root and can be accessed via URL
Environment is affected if running GoFilm version 1.0.0 or 1.0.1 with the SingleUpload endpoint exposed and files stored within web-accessible directory.
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 server-side file validation including magic byte verification, allowlist-based extension checking, filename sanitization, and store uploads outside the web root with script execution disabled. Consider deploying a WAF as an interim control.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13949 — 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-13949 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