CVE-2025-66480
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 · uneditedWildfire IM is an instant messaging and real-time audio/video solution. Prior to 1.4.3, a critical vulnerability exists in the im-server component related to the file upload functionality found in com.xiaoleilu.loServer.action.UploadFileAction. The application exposes an endpoint (/fs) that handles multipart file uploads but fails to properly sanitize the filename provided by the user. Specifically, the writeFileUploadData method directly concatenates the configured storage directory with the filename extracted from the upload request without stripping directory traversal sequences (e.g., ../../). This vulnerability allows an attacker to write arbitrary files to any location on the server's filesystem where the application process has write permissions. By uploading malicious files (such as scripts, executables, or overwriting configuration files like authorized_keys or cron jobs), an attacker can achieve Remote Code Execution (RCE) and completely compromise the server. This vulnerability is fixed in 1.4.3.
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 confidenceWildfire IM versions prior to 1.4.3 contain a path traversal vulnerability in the /fs endpoint's file upload functionality. The writeFileUploadData method in UploadFileAction concatenates user-supplied filenames directly with the storage directory without sanitizing directory traversal sequences (../), allowing attackers to write arbitrary files to any writable location on the server filesystem and achieve RCE.
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.4.3CVSS 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.
-
Determine installed Wildfirechat Im Server versionCheck the application's version file, startup logs, or API endpoint that reports version information. Common locations include: version manifest in the deployment directory, Docker image tags, or the server's /api/version endpoint if available.Affected if The installed version is lower than 1.4.3 (e.g., 1.4.2, 1.4.1, 1.4.0, or earlier).
-
Verify if /fs endpoint is exposed and accessibleSend an HTTP request to the /fs endpoint (e.g., GET https://your-server/fs) or check the server's reverse proxy and firewall rules to determine if this endpoint is internet-facing or accessible from untrusted networks.Affected if The /fs endpoint is publicly accessible without authentication or accessible to untrusted users.
-
Inspect upload directory configurationExamine the server configuration files (typically in conf/ or config/ directories) for the upload.file.directory or similar setting that defines where uploaded files are stored. Verify if this directory is writable by the application process.Affected if The upload directory is writable and the server runs with elevated privileges, allowing arbitrary file write to affect system directories.
-
Audit filesystem for files written outside intended upload directoryReview server filesystem logs and compare against the expected upload directory. Search for any files in system directories (e.g., /, /tmp, /var, /home, /root) or configuration directories that were created around the time of upload activity.Affected if Files exist outside the configured upload directory, indicating exploitation has occurred.
A user is affected if the Wildfirechat Im Server version is below 1.4.3 AND the /fs endpoint is accessible to untrusted users, allowing path traversal in uploaded filenames.
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.4.3
Upgrade to version 1.4.3 or later which includes proper filename sanitization to strip directory traversal sequences. As an immediate mitigation, restrict file upload permissions and monitor the /fs endpoint for suspicious upload patterns.
version 1.4.3
- 1. Backup the current im-server installation and database before proceeding with any upgrade.
- 2. Obtain version 1.4.3 or later of the im-server from the official WildfireChat repository (https://github.com/wildfirechat/im-server).
- 3. Stop the currently running im-server service.
- 4. Replace the existing im-server installation with the new version 1.4.3.
- 5. Review the application configuration to ensure compatibility with the new version.
- 6. Start the im-server service and verify it runs correctly.
- 7. Test the file upload functionality at the /fs endpoint to confirm path traversal is now properly sanitized.
- 8. Monitor logs for any errors or suspicious file upload attempts.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66480 — 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-66480 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