LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1332: HAMASTAR Technology|MeetingHub - Missing Authentication

MeetingHub developed by HAMASTAR Technology has a Missing Authentication vulnerability, allowing unauthenticated remote attackers to access specific API functions and obtain meeting-related information.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1332 is a missing authentication flaw in HAMASTAR Technology MeetingHub. An unauthenticated remote attacker may access certain API functions and obtain meeting-related information. The public record rates it medium severity. There is no evidence in the provided sources of active exploitation.

Executive priority

Treat as a near-term privacy and information-exposure risk if MeetingHub is used, especially if internet-facing. It does not currently warrant emergency response absent exploitation evidence, but ownership, exposure, and vendor remediation status should be confirmed promptly.

Technical view

The issue is CWE-306, Missing Authentication for Critical Function. The CVSS 4.0 vector is AV:N/AC:L/AT:N/PR:N/UI:N with low confidentiality impact only, score 6.9. The affected entry lists MeetingHub version “0,” but the provided data does not clearly explain version ranges or fixed releases.

Likely exposure

Exposure is most relevant where MeetingHub API endpoints are reachable from untrusted networks. The known impact is disclosure of meeting-related information through specific API functions. Organizations not running HAMASTAR MeetingHub are not affected based on the provided sources.

Exploitation context

The vulnerability is remotely reachable without authentication and requires low attack complexity. The sources do not provide exploit details, proof-of-concept status, observed exploitation, or affected endpoint specifics. KEV status is false in the provided bundle.

Researcher notes

Public data is limited. The CVE identifies missing authentication in specific APIs but does not name endpoints, fixed versions, or exploit availability. The affected version value “0” is ambiguous, so verification should rely on vendor or TWCERT advisory details rather than assumptions.

Mitigation direction

  • Identify whether HAMASTAR Technology MeetingHub is deployed.
  • Restrict MeetingHub API access to trusted networks where possible.
  • Review TWCERT and vendor guidance for fixed versions or configuration mitigations.
  • Monitor MeetingHub access logs for unauthenticated API activity.
  • Reduce public exposure of MeetingHub until vendor guidance is confirmed.

Validation and detection

  • Inventory MeetingHub instances and their software versions.
  • Confirm whether MeetingHub APIs are internet-facing.
  • Check access controls on API functions handling meeting information.
  • Review logs for anonymous requests to meeting-related API paths.
  • Track TWCERT advisories for version and remediation clarification.
Prepared
Confidence
medium
Sources
4

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-2026-1332 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
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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
0Timeline events
0ADP providers
3Source 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
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-1332Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HAMASTAR TechnologyMeetingHub0unaffected
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.