External risk intelligence

Tinxy WiFi Lock Controller Open Network Access Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2025-44619

This product is a Wi-Fi-enabled lock controller designed to operate on wireless networks. By its nature as an IoT device intended for network connectivity, it is a public-facing or network-reachable service by design, and the vulnerability involves an open Wi-Fi network configuration that is directly exposed to anyone within range of the signal.

Tinxy Wifi Lock Controller V1 Rf Firmware

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in a Wi-Fi enabled lock controller, which by default is configured to broadcast an open network. This could allow unauthorized access to the network without authentication, potentially impacting the security of connected systems.

Open Wi-Fi on lock controllers allows unauthorized network entry.
This matters because it impacts IoT device network security.
Confirm relevance; concern is unauthorized network access.

Attack Path

How an attacker could exploit the issue

An attacker could begin by locating a Tinxy WiFi Lock Controller that is configured to broadcast on an open Wi-Fi network. By joining this unauthenticated network, the attacker gains access to the controller. This exposure allows them to interact with the device and potentially exploit the vulnerability.

Entry requires proximity to an open Wi-Fi signal.
Triggered by connecting to the open Wi-Fi network.
Risk includes unauthorized access and control.

Live Threat

Current exploitation, exposure, and threat context

When configured for open Wi-Fi, the Tinxy WiFi Lock Controller v1 RF could allow unauthorized access to its network. This could enable attackers to interact with the device's network services without needing to authenticate.

Wi-Fi lock controller network.
Attackers join open Wi-Fi.
Unauthorized network access.

Operational Fix

Recommended remediation, mitigation, and detection steps

Infrastructure and security teams are likely responsible for addressing the Tinxy WiFi Lock Controller's open Wi-Fi network configuration. The first practical step is to identify all instances of this device, determine their network reachability and business criticality, and then assign ownership for remediation planning.

Infrastructure/Security teams own.
Verify network exposure and criticality.
Plan coordinated secure configuration.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the Tinxy WiFi Lock Controller v1 RF?

It is an Internet of Things (IoT) hardware component designed to manage electronic locking systems via wireless network connectivity. By integrating Wi-Fi communication, it allows the controller to bridge physical security access with digital commands. Users typically deploy these devices to enable remote management and automated entry control within a network environment.

What does CWE-284 mean for CVE-2025-44619?

CWE-284 refers to Improper Access Control. In the context of this vulnerability, it means the device fails to enforce necessary restrictions on who can interact with its internal services. Because the system lacks a mechanism to verify the identity of someone joining its network, it essentially permits unauthorized users to bypass authentication checks that would typically protect the device.

How can an attacker trigger this vulnerability?

The trigger occurs when an attacker connects to the open, unauthenticated Wi-Fi network broadcast by the controller. It is important to note that the vulnerability is specific to the device being configured in this open state; it is not triggered if the device is properly configured to require secure, authenticated wireless communication.

Do I need to worry about this device on my network?

According to Halo Surface Signal, this device is inherently network-reachable by design. Because it operates on wireless frequencies, the risk is tied to its physical and wireless proximity. If the device is broadcasting an open network, it is effectively exposed to anyone within range of the signal, regardless of whether it is intended to be internal or public-facing.

How should I respond if I use this controller?

Begin by creating an inventory of all instances of the Tinxy WiFi Lock Controller within your environment. Once identified, evaluate how these devices are currently connected to your infrastructure and assess their overall criticality. Prioritize securing any units found broadcasting an open network by coordinating with your team to implement proper authentication and secure network configurations.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.