CVE-2026-2670
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 identified in Advantech WISE-6610 1.2.1_20251110. Affected is an unknown function of the file /cgi-bin/luci/admin/openvpn_apply of the component Background Management. Such manipulation of the argument delete_file leads to os command injection. The attack can be executed remotely. The exploit is publicly available and might 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 Advantech WISE-6610 IoT gateway (v1.2.1_20251110) in the /cgi-bin/luci/admin/openvpn_apply handler. The delete_file parameter is not properly sanitized, allowing remote attackers to execute arbitrary OS commands via the web interface.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 device model is WISE-6610Access the device web interface or check the device label/serial number. The vulnerability applies specifically to the WISE-6610 IoT gateway model.Affected if Device is not an Advantech WISE-6610 gateway, then not affected by this specific CVE.
-
Check installed firmware versionLog into the device web UI and navigate to System > Firmware or Status page to view the current firmware version. Compare against v1.2.1_20251110.Affected if Firmware version is v1.2.1_20251110 exactly, then the device is running the affected version.
-
Verify web interface (luci) is enabledAttempt to access the device at /cgi-bin/luci/admin/ or the main login page. The vulnerability exists in the luci web interface CGI handler.Affected if Web interface is disabled or inaccessible, then the attack surface for this specific vulnerability may not be reachable.
-
Check if OpenVPN functionality is presentLook for OpenVPN configuration options in the device web UI under Network or VPN sections. The vulnerable handler is /cgi-bin/luci/admin/openvpn_apply.Affected if The openvpn_apply handler exists on the device, indicating OpenVPN module is loaded and the vulnerable endpoint is present.
-
Assess network accessibility of management interfaceDetermine if the device web interface is exposed to untrusted networks. Check firewall rules, VLAN configuration, or ACLs controlling access to the device IP on HTTP/HTTPS ports.Affected if The management web interface is reachable from untrusted networks, then remote exploitation is possible.
The device is affected if it is an Advantech WISE-6610 running firmware v1.2.1_20251110 with the luci web interface enabled and accessible, regardless of whether OpenVPN is actively configured.
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 dataSince vendor did not respond, apply compensating controls: restrict network access to the device's management interface via firewall/ACLs, disable the web UI if not required, or place device in isolated network segment.
- 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-2026-2670 — 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-2026-2670 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