# CVE-2025-5106: Fujian Kelixun Filename fax_view.php os command injection

> Remote attackers can execute arbitrary OS commands via the fax_file argument in fax_view.php of Fujian Kelixun.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2025
- **Updated:** 23 May 2025
- **Also known as:** GHSA-3v74-7fxr-9p4j

## What is CVE-2025-5106?

CVE-2025-5106 is a medium-severity command injection vulnerability in Fujian Kelixun, published on 23 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-5106?


## How do I fix CVE-2025-5106?

No fix has been published for CVE-2025-5106 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5106 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5106 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5106 and fix it if it is affected.

What it is: CVE-2025-5106 is a medium-severity command injection vulnerability in Fujian Kelixun, published on 23 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5106 exists.

Affected product: Fujian Kelixun. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5106/ (Markdown: https://insights.sbomify.com/CVE-2025-5106/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5106
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5106
- OSV: https://osv.dev/vulnerability/CVE-2025-5106

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5106/
Summaries are generated and may contain mistakes; the official description above is the record.