# CVE-2025-6102: Wifi-soft UniBox Controller logout.php os command injection

> Remote attackers can execute arbitrary OS commands via the mac_address parameter in logout.php of Wifi-soft UniBox Controller.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2025
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-jxm4-rp8w-49rh

## What is CVE-2025-6102?

CVE-2025-6102 is a high-severity command injection vulnerability in Wifi-soft UniBox Controller, published on 16 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in Wifi-soft UniBox Controller up to 20250506. Affected by this vulnerability is an unknown functionality of the file /authentication/logout.php. The manipulation of the argument mac_address leads to os command injection. The attack can be launched 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-6102?


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

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

## Is CVE-2025-6102 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6102 is a high-severity command injection vulnerability in Wifi-soft UniBox Controller, published on 16 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6102 exists.

Affected product: Wifi-soft UniBox Controller. 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-6102/ (Markdown: https://insights.sbomify.com/CVE-2025-6102/index.md)
```

## Sources

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

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