The front door has no lock, the vendor left town, and the device it guards can flip breakers on a solar site
CVE-2026-61884 is a textbook authentication-bypass-by-alternate-path (CWE-288) in the Tycon Systems TPDIN-Monitor-WEB2 web management interface, confirmed in firmware 2.3.9 and — per CISA's ICSA-26-202-01 — every prior build. Submit the login form with empty username and empty password and the server hands back a valid administrative session cookie. The dashboard exposes power-relay toggles, device reboot, remote-access service configuration, network settings, and — as a bonus second bug — cleartext display of stored system credentials that can pivot to adjacent gear.
The vendor CVSS of 9.8 is technically correct for the primitive (network, no auth, no UI, full CIA impact) but flatters the real-world picture. Two facts collapse the gap: (1) this is niche OT/telecom hardware — PoE-injected DIN-rail monitors deployed at cell sites, solar arrays, and remote radio huts, not internet-facing enterprise infrastructure, and (2) Tycon has discontinued the product and refused to engage CISA — there will be no patch, ever. That flips the analysis from 'fix it fast' to 'get it off the network permanently.' We assess HIGH because the blast radius on the small population that *is* exposed is physical/operational (cutting power to a remote radio, damaging a battery bank), but the affected population itself is a rounding error on any enterprise fleet.
4 steps from start to impact.
Locate an exposed TPDIN-Monitor-WEB2
http.title:"TPDIN" or http.favicon.hash yield the population in seconds. Historically the device count in public scanners is in the low hundreds globally.- Device reachable from attacker network position (usually public internet, occasionally VPN/internal)
- Most deployments sit behind a cellular APN, site VPN, or NAT with no port forward
- Product line is niche — Shodan population is small and easy to enumerate defensively too
Submit blank credentials to the login endpoint
curl or any HTTP client, POST an empty username and empty password to the login handler. The server issues an authenticated session cookie without validating the fields server-side. No exploit framework or CVE-specific tool needed — this is a two-line curl request.- HTTP(S) reachability to the management interface
- Vulnerable firmware ≤ 2.3.9 (i.e., every shipped version)
- None at the vuln layer — the bug requires zero skill
- Rate-limiters or fronting reverse proxies (rare on this class of device) would slow brute discovery but not the exploit itself
Harvest cleartext credentials from the configuration page
- Admin session from step 2
- Operator populated the credential fields (most did — that's the product's purpose)
- Credentials may be site-scoped and useless off-net
- Some deployments leave defaults or dummy values
Toggle relays, reconfigure network, or brick the device
- Physical loads attached to the controlled relays (the default deployment pattern)
- Site operators may notice power drops via out-of-band monitoring (NMS, tower alarms)
- Battery/UPS protection circuits may override sustained abuse
TPDIN-MONITOR-WEB2 and TPDIN2. Also run a Nmap HTTP-title sweep across site management VLANs for TPDIN. HIGH verdict → noisgate mitigation SLA is 30 days, but for a no-patch-ever OT device you want inventory closed in the first 72 hours so the isolation work can start.- Changing the admin password — the bypass does not use the password field at all. Setting a stronger password is theater.
- Enabling HTTPS on the device — TLS protects the credentials in transit but the bypass is a server-side logic flaw. Encrypting the empty-string POST does not help.
- Web Application Firewall signatures — you could write a rule to block empty-field POSTs, but few enterprises put a WAF in front of a $300 OT monitor, and the device typically sits behind a site router with no WAF plane.
- Waiting for a vendor patch — Tycon has discontinued the product and did not respond to CISA. No fix is coming.
The supporting signals.
| In-the-wild exploitation | None reported as of 2026-07-25. Disclosure is 24 hours old and the target population is small; expect opportunistic scanning within days. |
|---|---|
| Public PoC | No dedicated PoC repo published. The exploit is trivially reproducible with curl --data 'username=&password=' — no tooling required. Researcher Abdiwelli Guled credited by CISA. |
| EPSS | Not yet scored (CVE published 2026-07-24). Expect a low percentile initially due to narrow exposure, rising if scanners start indexing the banner. |
| CISA KEV | Not listed. Unlikely to be added — federal exposure to this OEM is minimal. |
| CVSS | Vendor 9.8 — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Reads as internet-worm-grade; in practice the AV:N is only meaningful for the sliver of units directly reachable. |
| Affected versions | All firmware through 2.3.9, per CISA ICSA-26-202-01. No fixed version — product discontinued. |
| Fixed version | None. Ever. Tycon Systems did not respond to CISA coordination and has EOL'd the product line. |
| Exposure data | Shodan/Censys historical counts for TPDIN-Monitor-WEB2 fingerprints trend in the low hundreds globally. No credible enterprise deployment at scale; concentrations are in telecom tower sites, solar/off-grid installations, ISP remote huts. |
| Disclosure | CISA advisory ICSA-26-202-01, published 2026-07-24. CWE-288 (Authentication Bypass Using an Alternate Path or Channel). |
| Companion vuln | Cleartext credential storage/display in same UI — same advisory. Amplifies blast radius via credential reuse. |
Sources.
- CISA ICSA-26-202-01 — Tycon Systems TPDIN-Monitor-WEB2
- ISSSource — No Fix for Tycon Systems TPDIN-Monitor-WEB2
- Assurant Cyber — ICSA-26-202-01 analysis
- Tycon Systems TPDIN-Monitor-WEB2 product page
- TPDIN-Monitor-WEB2 firmware downloads
- TPDIN-Monitor-WEB2 spec sheet (PDF)
- NCSA Cyber Threat Intelligence 22 July 2026
- MITRE CWE-288 — Authentication Bypass Using an Alternate Path or Channel
Why this verdict
- Trivial exploitability, zero prerequisites: unauth remote, no user interaction, exploit is a single curl one-liner. Nothing about the vuln layer justifies a downgrade.
- Installed-base narrowing (-1.0): niche discontinued PoE-injected DIN-rail monitor. Public scanner population is in the hundreds, not the millions — most enterprise fleets have zero units.
- Deployment-position narrowing (-0.5): the majority of remaining units live behind cellular APNs, site VPNs, or NAT with no inbound rules. Public exposure is a subset of an already small base.
- Role multiplier — the device IS the high-value role (+0.3): unlike a typical LOB app, this thing controls physical relays feeding radios, cameras, and battery chargers. Chain outcome on a compromised unit is loss of service or equipment damage at a remote site, not just data theft. That floors the verdict at HIGH and prevents further downgrade.
- Role multiplier — no supply-chain or fleet amplification: compromise of one TPDIN-Monitor-WEB2 does not pivot to a domain, hypervisor, IdP, or CI pipeline. Blast radius is bounded at the site level, which is why the floor is HIGH and not CRITICAL.
- No-patch-ever status: because Tycon has EOL'd the product, this is not a patch-cycle problem — it is a decommission-or-isolate problem. Treat as permanent risk debt for anyone who owns one.
Why not higher?
Not CRITICAL because the installed-base share is a rounding error on any enterprise fleet and the blast radius does not amplify beyond the single site the device controls. There is no domain, tenant, hypervisor, or supply-chain pivot — the ceiling on damage is 'one remote hut goes dark.'
Why not lower?
Not MEDIUM because the exploit is a two-line curl, requires no auth, needs no user interaction, and — for the units that ARE publicly reachable — ends in physical control of power relays. There is also no patch coming, so the risk does not decay over time the way a normal MEDIUM would.
Crowdsourced verification payload.
Run from an auditor workstation with network reachability to the target device (site LAN, jump host, or authorized VPN). Invoke as ./check_tpdin.sh 10.20.30.40 where the argument is the device IP or hostname. Requires only curl and network access — no credentials, no root.
#!/usr/bin/env bash
# noisgate verification for CVE-2026-61884
# Tycon Systems TPDIN-Monitor-WEB2 auth-bypass check
# Usage: ./check_tpdin.sh <host-or-ip> [port]
set -u
HOST="${1:-}"
PORT="${2:-80}"
if [[ -z "$HOST" ]]; then
echo "Usage: $0 <host-or-ip> [port]" >&2
exit 2
fi
BASE="http://${HOST}:${PORT}"
CJAR="$(mktemp)"
trap 'rm -f "$CJAR"' EXIT
# 1) Confirm the device is a TPDIN-Monitor-WEB2 by banner/title
TITLE=$(curl -s --max-time 5 "$BASE/" | grep -oiE '<title>[^<]*</title>' | head -n1)
if ! echo "$TITLE" | grep -qi 'TPDIN'; then
echo "UNKNOWN - host at $BASE does not appear to be a TPDIN-Monitor-WEB2 (title: $TITLE)"
exit 3
fi
# 2) Attempt the empty-credential bypass. The exact login path varies by
# firmware build; try the two documented endpoints.
for PATH_ in "/login.cgi" "/cgi-bin/login"; do
CODE=$(curl -s -o /dev/null -w '%{http_code}' \
-c "$CJAR" --max-time 5 \
-X POST --data 'username=&password=' \
"${BASE}${PATH_}" || true)
# Any 2xx/3xx that also sets a session cookie is a positive.
if [[ "$CODE" =~ ^(200|301|302|303)$ ]] && grep -qiE 'session|sid|auth' "$CJAR"; then
echo "VULNERABLE - empty credentials to ${PATH_} returned $CODE and issued a session cookie"
exit 1
fi
done
echo "PATCHED - device did not accept empty credentials on any known login path (note: no vendor patch exists; result may reflect a non-default login handler)"
exit 0