LiveActive security incident?Get immediate response
CVE Record

CVE-2024-40087: Vilo 5 Mesh WiFi System <= 5.16.1.33 is vulnerable to Insecure Permissions.

Vilo 5 Mesh WiFi System <= 5.16.1.33 is vulnerable to Insecure Permissions. Lack of authentication in the custom TCP service on port 5432 allows remote, unauthenticated attackers to gain administrative access over the router.

CriticalCVSS 9.6Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This issue can let an unauthenticated network attacker gain administrative control of a Vilo 5 Mesh WiFi router. For executives, the concern is loss of control over home or small-office network infrastructure, with possible confidentiality, integrity, and availability impact.

Executive priority

Prioritize within the next maintenance window, sooner if affected routers are reachable from untrusted networks or support critical connectivity.

Technical view

CVE-2024-40087 is a CWE-306 missing-authentication flaw in a custom TCP service on port 5432 affecting Vilo 5 Mesh WiFi System firmware up to 5.16.1.33. The published CVSS 3.1 score is 9.6 with no privileges or user interaction required.

Likely exposure

Exposure appears limited to Vilo 5 Mesh WiFi System devices running firmware <= 5.16.1.33. The source bundle does not provide CPEs or complete vendor/product metadata, so inventory confirmation is required.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Public vulnerability details exist, so defenders should treat reachable affected devices as high priority without claiming in-the-wild exploitation.

Researcher notes

Evidence is strong for missing authentication and high impact, but incomplete for exact vendor metadata, CPEs, patched versions, and real-world exploitation. Avoid assuming a fix exists until vendor guidance confirms it.

Mitigation direction

  • Identify Vilo 5 Mesh WiFi devices and record firmware versions.
  • Check Vilo or vendor guidance for firmware updates or official mitigations.
  • Block TCP 5432 access from untrusted networks where feasible.
  • Restrict router administrative access to trusted management networks.
  • Replace or isolate affected devices if no vendor fix is available.

Validation and detection

  • Confirm whether any Vilo 5 Mesh WiFi devices run firmware <= 5.16.1.33.
  • Validate that TCP 5432 is not reachable from untrusted segments.
  • Review router configuration for unexpected administrative access changes.
  • Monitor network traffic for unusual connections to affected routers.
  • Track the CVE record and vendor advisories for updated remediation guidance.
Prepared
Confidence
medium
Sources
3

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-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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-2024-40087 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.6 (3.1)
Known Exploited
No
Published

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

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
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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.6CVSS 3.1CriticalCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H2.86CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.6Critical
CVSS 3.1 vector shape for CVE-2024-40087Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
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-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.