CVE-2025-5106
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 found in Fujian Kelixun 1.0. It has been classified as critical. This affects an unknown part of the file /app/fax/fax_view.php of the component Filename Handler. The manipulation of the argument fax_file leads to os command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may 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 · moderate confidenceFujian Kelixun 1.0 contains an OS command injection vulnerability in /app/fax/fax_view.php via the fax_file parameter. Remote attackers can execute arbitrary operating system commands by manipulating this filename handler argument.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 Fujian Kelixun installationLocate the web application root directory and check for the presence of the Kelixun application files. Common paths may include /app/ or check your web server document root for the Kelixun application structure.Affected if The Fujian Kelixun 1.0 application is installed on the server.
-
Verify vulnerable file existsInspect the file system for /app/fax/fax_view.php within the Kelixun application directory. Use a file search command such as 'find / -path *fax/fax_view.php' or locate the file via your file manager.Affected if The file /app/fax/fax_view.php exists in the application directory.
-
Confirm fax_file parameter is acceptedExamine the fax_view.php source code to verify it accepts a fax_file GET or POST parameter, or test the endpoint by sending a request with a fax_file parameter (e.g., /app/fax/fax_view.php?fax_file=test).Affected if The fax_view.php script processes the fax_file parameter without requiring authentication.
-
Check for input validation on fax_fileReview the fax_view.php code for sanitization or validation logic applied to the fax_file parameter before use in file operations or system calls.Affected if No input validation or sanitization is performed on the fax_file parameter, allowing arbitrary input to be passed to system commands.
The system is affected if Fujian Kelixun 1.0 is installed, the file /app/fax/fax_view.php exists, and the fax_file parameter is processed without proper input validation, allowing command injection.
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 input validation and sanitization on the fax_file parameter to prevent command injection, or deploy a web application firewall as a compensating control until the code is fixed.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5106 — 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-5106 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