dbcve.org
Thingino FirmwareOperating system · Thingino

CVE-2026-26213

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to after 2026-03-15 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
thingino-firmware versions up to the firmware-2026-03-16 release contains an unauthenticated os command injection vulnerability in the WiFi captive portal CGI script that allows remote attackers to execute arbitrary commands as root by injecting malicious code through unsanitized HTTP parameter names. Attackers can exploit the eval function in parse_query() and parse_post() functions to achieve remote code execution and perform privileged configuration changes including root password reset and SSH authorized_keys modification, resulting in full persistent device compromise.

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 confidence

thingino-firmware up to the firmware-2026-03-16 release contains an unauthenticated OS command injection vulnerability in the WiFi captive portal CGI script. Attackers exploit unsanitized HTTP parameter names passed to eval() functions in parse_query() and parse_post(), achieving root-level remote code execution and persistent device compromise.

MitigationImplement strict input validation and sanitization on all HTTP parameter names, replace or remove dangerous eval() calls, and update to a patched firmware version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Thingino FirmwareOperating system
Affected:<= 2026-03-15

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify firmware type and version
    Check the device's firmware version or build date. This is typically available via the web UI under 'System > Firmware' or by checking /etc/version or /etc/os-release on the device shell if accessible.
    Affected if The device runs thingino-firmware with version/build date <= 2026-03-15 or the 2026-03-16 release candidate.
  2. Locate the WiFi captive portal CGI script
    On the thingino firmware, locate the WiFi captive portal CGI script. Common paths may include /www/cgi-bin/captive or similar. Check for files handling WiFi captive portal functionality.
    Affected if The CGI script exists on the device filesystem.
  3. Verify the vulnerable eval() usage
    Inspect the CGI script source code and search for eval() function calls within parse_query() and parse_post() functions. Look for patterns where HTTP parameters are passed directly to eval() without sanitization.
    Affected if The script contains eval() calls on unsanitized HTTP parameter names in parse_query() or parse_post() functions.
  4. Check if WiFi captive portal is enabled
    Review the device configuration to determine if the WiFi captive portal feature is enabled. This may be visible in the web UI under WiFi settings or in the device's configuration files.
    Affected if The WiFi captive portal is enabled and accessible to network users.

A defender is affected if the device runs thingino-firmware <= 2026-03-15 and has the WiFi captive portal CGI script present with the vulnerable eval() patterns, allowing unauthenticated command injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2026-03-15
Interim mitigation

Implement strict input validation and sanitization on all HTTP parameter names, replace or remove dangerous eval() calls, and update to a patched firmware version.

Recommended fix High confidence

firmware-2026-03-16 or later

  1. Identify the current Thingino Firmware version installed on the device
  2. Access the device's firmware update mechanism (web UI, OTA, or manufacturer-provided update tool)
  3. Upgrade to firmware-2026-03-16 or later release that addresses the command injection vulnerability in the WiFi captive portal CGI script
  4. Verify the upgrade was successful by checking the firmware version
  5. After upgrade, validate that the parse_query() and parse_post() functions no longer use unsanitized input in eval() calls

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Thingino Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26213 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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