CVE-2025-6102
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 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.
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 confidenceOS command injection vulnerability in Wifi-soft UniBox Controller's /authentication/logout.php endpoint. The mac_address parameter is not properly sanitized before being used in a system command, allowing an unauthenticated remote attacker to execute arbitrary OS commands. A public exploit exists.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Wifi-soft UniBox Controller is installedIdentify the installed product by reviewing web server response headers, title tags, or consulting inventory systems for 'UniBox Controller' or 'Wifi-soft' softwareAffected if The system is running Wifi-soft UniBox Controller
-
Verify logout.php endpoint existsCheck if /authentication/logout.php is accessible on the management interface (e.g., curl -s http://target/authentication/logout.php)Affected if The endpoint returns a valid HTTP response rather than a 404
-
Inspect logout.php for unsafe command executionReview the source code of logout.php if accessible, looking for system(), exec(), shell_exec(), or passthru() calls that incorporate the mac_address parameter without sanitizationAffected if The code uses mac_address in a shell command without parameterized queries or input validation
-
Check if management interface is network exposedReview firewall rules or network access lists to determine if the UniBox management interface (typically ports 80/443) is reachable from untrusted networksAffected if The management interface is accessible from outside trusted networks without authentication barrier
-
Verify no WAF/IPS rule blocks the logout endpointReview WAF or IPS configurations to confirm whether /authentication/logout.php or parameter-based requests are being blocked or sanitizedAffected if No protective rule exists and the endpoint remains directly accessible
The environment is affected if it runs Wifi-soft UniBox Controller with the logout.php endpoint accessible and the mac_address parameter processed in an unsafe manner within system commands.
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 dataUntil vendor provides a patch, implement defense-in-depth: block the affected endpoint at the WAF/IPS layer, restrict network access to the management interface, and consider disabling the logout functionality if feasible. Alternatively, manually patch the logout.php to use parameterized calls or input validation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6102 — 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-6102 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