cve.bz

CVE-2026-123787 nexmoe vidbee: Improper Access Control

2.1 lowEPSS 0.3%

Low (2.1) in nexmoe vidbee. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A weakness has been identified in nexmoe VidBee up to 1.3.13/2.0.2. The affected element is an unknown function of the file apps/desktop/src/main/local-api.ts of the component Local HTTP Service. Executing a manipulation can lead to information disclosure. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 2.2.0 is sufficient to fix this issue. This patch is called 141b8d39c1c11da4589264f814cee077df81e7f6. It is suggested to upgrade the affected component.

Severity

CVSS 4.0

2.1 low
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-123787 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123787?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123787?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123787 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nexmoe VidBee1.3.0
nexmoe VidBee1.3.1
nexmoe VidBee1.3.2
nexmoe VidBee1.3.3
nexmoe VidBee1.3.4
nexmoe VidBee1.3.5
nexmoe VidBee1.3.6
nexmoe VidBee1.3.7
nexmoe VidBee1.3.8
nexmoe VidBee1.3.9
nexmoe VidBee1.3.10
nexmoe VidBee1.3.11
nexmoe VidBee1.3.12
nexmoe VidBee1.3.13
nexmoe VidBee2.0.0
nexmoe VidBee2.0.1
nexmoe VidBee2.0.2

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17), CWE-200 (59).

References

Check your stackJSON