LiveActive security incident?Get immediate response
CVE Record

CVE-2023-2759: TAPHOME Improper Authentication in Core Platform

A hidden API exists in TapHome's core platform before version 2023.2 that allows an authenticated, low privileged user to change passwords of other users without any prior knowledge. The attacker may gain full access to the device by using this vulnerability.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-2759 lets a low-privileged authenticated user in TapHome Core Platform change other users’ passwords through a hidden API. In affected deployments, that could turn a basic account into full device access. The issue is rated high severity and applies to versions before 2023.2.

Executive priority

Treat this as a high-priority remediation item if TapHome is used in operational or building-control environments. A compromised low-privileged account may become full device access, creating business risk beyond normal account misuse.

Technical view

The CVE describes improper authentication, CWE-863, in TapHome Core Platform before 2023.2. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where TapHome Core Platform before 2023.2 is deployed and low-privileged users can authenticate to it. The provided sources do not list CPEs, deployment modes, or internet-exposure details.

Exploitation context

The sources support authenticated, low-privilege abuse, not unauthenticated compromise. CISA KEV is false in the bundle, and no provided source states active exploitation or public exploit availability.

Researcher notes

Evidence is limited to CVE metadata and the Claroty disclosure reference. The affected version boundary is clear, but the bundle does not provide endpoint details, product configuration nuance, exploit telemetry, or vendor mitigation text beyond the pre-2023.2 condition.

Mitigation direction

  • Inventory TapHome Core Platform deployments and identify versions before 2023.2.
  • Prioritize updating affected TapHome Core Platform instances to 2023.2 or later.
  • Review TapHome or Claroty guidance before relying on compensating controls.
  • Limit platform access to trusted users and administrative network paths until remediated.
  • Review low-privileged accounts and remove unnecessary access.

Validation and detection

  • Confirm whether any TapHome Core Platform instance is older than 2023.2.
  • Verify low-privileged users cannot change other users’ passwords after remediation.
  • Review audit logs for unexpected password changes or privilege escalation indicators.
  • Check exposed management interfaces and authentication paths for unnecessary reachability.
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-863: 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-2023-2759 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-2759Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
TAPHOMECore Platform0.0unaffected
Weakness

CWE details

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

CWE-863 · source CWE mapping

Incorrect Authorization

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