LiveActive security incident?Get immediate response
CVE Record

CVE-2025-44619: Tinxy WiFi Lock Controller v1 RF was discovered to be configured to transmit on an open Wi-Fi network, allo...

Tinxy WiFi Lock Controller v1 RF was discovered to be configured to transmit on an open Wi-Fi network, allowing attackers to join the network without authentication.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-44619 describes a Tinxy WiFi Lock Controller v1 RF configuration that uses an open Wi-Fi network. An attacker within wireless range could join without authentication, creating a serious risk to confidentiality and control of connected lock-related functions.

Executive priority

Treat as urgent for environments using this lock controller, especially where physical access or sensitive areas depend on it. Prioritize identification, isolation, and vendor guidance. Do not assume a software fix exists based on current public sources.

Technical view

The CVE record reports CWE-284 improper access control: the device transmits on an open Wi-Fi network. CVSS 3.1 is 9.1, network attack vector, low complexity, no privileges, no user interaction, with high confidentiality and integrity impact. Public details do not name patched versions or vendor remediation.

Likely exposure

Exposure is most likely where Tinxy WiFi Lock Controller v1 RF devices are deployed and their wireless network is reachable. The CVE data does not provide CPEs, version ranges beyond the named v1 RF, or deployment guidance.

Exploitation context

No CISA KEV listing is provided, and the source bundle does not state active exploitation. The risk is practical because joining an open Wi-Fi network requires no credentials, but the attacker generally must be within wireless range.

Researcher notes

The public CVE data is sparse: affected vendor/product fields are listed as n/a, while the description names Tinxy WiFi Lock Controller v1 RF. References include Tinxy and researcher-related pages, but no detailed advisory, PoC, patch note, or exploitation evidence is included.

Mitigation direction

  • Identify any deployed Tinxy WiFi Lock Controller v1 RF devices.
  • Check Tinxy or device support channels for official firmware, configuration, or replacement guidance.
  • Restrict physical and wireless proximity to affected devices where possible.
  • Segment lock controller networks from business and sensitive systems.
  • Monitor nearby wireless networks for unexpected open SSIDs associated with controllers.

Validation and detection

  • Inventory sites for Tinxy WiFi Lock Controller v1 RF devices.
  • Confirm whether any controller advertises or uses an open Wi-Fi network.
  • Review network segmentation around affected controller deployments.
  • Check vendor sources for updates or advisories referencing CVE-2025-44619.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-44619 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2025-44619Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.