LiveActive security incident?Get immediate response
CVE Record

CVE-2025-70340: A Broken Access Control vulnerability exists in ThingsBoard Professional Edition (PE) 4.21 and below, withi...

A Broken Access Control vulnerability exists in ThingsBoard Professional Edition (PE) 4.21 and below, within the Alarms comments functionality. An authenticated customer user can manipulate the respective API request parameters to create or modify system-generated alarm comments. This allows unauthorized impersonation of system messages and modification of trusted system-owned data, resulting in vertical privilege escalation and potential integrity violations.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

An authenticated ThingsBoard customer user may be able to make alarm comments appear system-generated or alter trusted system comments. This could mislead operators, corrupt incident records, and undermine automated or human decisions based on alarm history. The supplied sources do not establish confidentiality or availability impact.

Executive priority

Treat this as a prompt integrity remediation rather than a confirmed emergency. Prioritize systems where alarm records drive incident response, safety decisions, compliance evidence, or automation. Escalate urgency if suspicious comment changes are found.

Technical view

CVE-2025-70340 is a broken access control issue in ThingsBoard Professional Edition 4.21 and below. Insufficient authorization within Alarms comments reportedly permits authenticated customer users to manipulate API request parameters and create or modify system-owned comments, causing vertical privilege escalation and integrity violations.

Likely exposure

Potential exposure is limited to organizations running ThingsBoard Professional Edition 4.21 or below where authenticated customer users can access Alarms comments. The supplied data does not identify affected configurations, deployment prevalence, or whether Community Edition is affected.

Exploitation context

The supplied bundle does not report active exploitation, public exploit availability, or KEV listing. An attacker reportedly requires an authenticated customer account and access to the affected functionality. Absence of reported exploitation does not establish that exploitation has never occurred.

Researcher notes

The source description supports an authenticated vertical privilege escalation affecting alarm-comment integrity. However, no CVSS vector, CWE assignment, affected CPE, fixed version, patch reference, root-cause detail, or exploitation evidence is supplied. The unusual version string “4.21” should be confirmed with ThingsBoard guidance rather than reinterpreted.

Mitigation direction

  • Confirm the deployed ThingsBoard edition and version against the affected range.
  • Check ThingsBoard guidance for a fixed release; no confirmed fix is identified in the supplied sources.
  • Apply least-privilege restrictions to customer access involving Alarms comments where operationally feasible.
  • Monitor system-generated alarm comments for unexpected authorship, edits, or inconsistent audit history.

Validation and detection

  • Inventory all ThingsBoard Professional Edition instances and record their exact versions.
  • Review customer roles and permissions associated with Alarms comments.
  • Audit alarm comment history for customer-linked changes to system-owned records.
  • In an authorized test environment, verify customer users cannot create or modify system-generated comments.
  • Revalidate authorization behavior after applying vendor-confirmed remediation.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. 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-2025-70340 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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