cve.bz

CVE-2023-1083 welotec

9.8 criticalEPSS 0.7%

Critical (9.8) in welotec. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
An unauthenticated remote attacker who is aware of a MQTT topic name can send and receive messages, including GET/SET configuration commands, reboot commands and firmware updates.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2024-04-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.
CWE
CWE-306 Missing Authentication for Critical Functionality
OWASP Top 10
A07:2025 Authentication Failures
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-2023-1083 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-1083?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-1083?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-2023-1083 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
Welotec TK515Lbefore v2.3.0.r5542
Welotec TK515L Setbefore v2.3.0.r5542
Welotec TK515L-Wbefore v2.3.0.r5542
Welotec TK515L-W Setbefore v2.3.0.r5542
Welotec TK525Lbefore v2.3.0.r5542
Welotec TK525L Setbefore v2.3.0.r5542
Welotec TK525L-Wbefore v2.3.0.r5542
Welotec TK525L-W Setbefore v2.3.0.r5542
Welotec TK525Ubefore v2.3.0.r5542
Welotec TK525U Setbefore v2.3.0.r5542
Welotec TK525Wbefore v2.3.0.r5542
Welotec TK525W Setbefore v2.3.0.r5542
Welotec TK535L1before v2.3.0.r5542
Welotec TK535L1 Setbefore v2.3.0.r5542

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-166 Force the System to Reset Values Severity: Medium
  • CAPEC-216 Communication Channel Manipulation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON