LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24161: TOTOLINK CA300-PoE V6.2c.884 was discovered to contain a command injection vulnerability via the webWlanIdx...

TOTOLINK CA300-PoE V6.2c.884 was discovered to contain a command injection vulnerability via the webWlanIdx parameter in the setWebWlanIdx function.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE describes unauthenticated network command injection in TOTOLINK CA300-PoE firmware V6.2c.884. If exposed, an attacker could potentially run operating-system commands on the device, risking compromise, outage, or pivoting. The sources do not identify a vendor patch or active exploitation.

Executive priority

Prioritize discovery and exposure reduction now for any CA300-PoE deployment. The issue is critical by CVSS and remotely reachable, but patch status and exploitation evidence are incomplete in the provided sources.

Technical view

CVE-2023-24161 is CWE-77 command injection in the webWlanIdx parameter handled by setWebWlanIdx. CVSS v3.1 is 9.8, with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where TOTOLINK CA300-PoE devices running V6.2c.884 have the affected web management interface reachable from untrusted networks. The CVE record lacks CPE data and broader affected-version detail.

Exploitation context

The source bundle includes a public vulnerability write-up and critical CVSS scoring, but KEV is false and no cited source confirms active exploitation. Treat internet-reachable management interfaces as urgent risk because exploitation requires no privileges or user interaction.

Researcher notes

The public record names webWlanIdx in setWebWlanIdx and CWE-77. The bundle does not provide CPEs, authentication context beyond CVSS, fixed versions, or vendor advisory details. Avoid assuming affected models beyond CA300-PoE V6.2c.884.

Mitigation direction

  • Inventory TOTOLINK CA300-PoE devices and confirm firmware versions.
  • Check TOTOLINK or reseller guidance for fixed firmware or official mitigations.
  • Remove administrative web interfaces from internet and untrusted network exposure.
  • Restrict management access to trusted administrative networks only.
  • Plan replacement or isolation where no vendor-supported fix exists.

Validation and detection

  • Confirm whether any CA300-PoE device runs firmware V6.2c.884.
  • Identify whether the web management interface is reachable from untrusted networks.
  • Review asset records for NAT, firewall, VPN, or remote-management exposure.
  • Check device logs and configuration history for unexpected administrative changes.
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-77: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-24161 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.8 (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: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
0Timeline events
0ADP providers
2Source links

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.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-24161Attack 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:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
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-77 · source CWE mapping

Improper Neutralization of Special Elements used in a Command ('Command Injection')

Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.