CVE-2026-111654 in FastBeeinfo

Summary

by MITRE • 10/16/2026

FastBee through 2.1.0 contains an insecure direct object reference vulnerability that allows authenticated low-privilege users to access other users' device groups because GroupController queries lack owner checks. Attackers, including self-registered users, can supply sequential group IDs to read, overwrite, reassign, rewrite device associations of, or delete other users' groups.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 10/16/2026

The vulnerability identified in FastBee versions up to 2.1.0 represents a critical failure in access control mechanisms, specifically classified as an Insecure Direct Object Reference (IDOR). This flaw stems from the GroupController component within the application architecture, which processes requests related to device group management without implementing adequate authorization checks. The core technical deficiency lies in the absence of owner verification logic when querying or modifying data associated with specific group identifiers. Consequently, the system relies solely on the presence of a valid authentication token rather than validating whether the authenticated user possesses legitimate ownership rights over the requested resource. This design oversight allows any authenticated user to interact directly with object references that belong to other users in the system.

From an operational perspective, this vulnerability enables low-privilege attackers, including self-registered accounts which typically have minimal permissions, to perform unauthorized actions against high-value resources. By supplying sequential or guessed group identifiers, an attacker can read sensitive configuration data belonging to other tenants or organizations using the platform. Beyond mere information disclosure, the lack of write restrictions permits more severe impacts such as overwriting existing configurations, reassigning device associations to different groups under malicious control, rewriting critical parameters, or deleting entire groups entirely. This level of access undermines the multi-tenancy isolation that is fundamental to IoT management platforms like FastBee, potentially leading to significant data breaches and operational disruption for legitimate users.

The security implications extend beyond simple data leakage. The ability to reassign device associations allows an attacker to hijack control over physical or virtual devices belonging to other entities. This could result in the manipulation of industrial processes, unauthorized surveillance through IoT cameras, or the inclusion of compromised devices into botnets if those groups are used for command and control operations. Furthermore, the deletion capability poses a risk of denial-of-service against specific organizational units within the platform, disrupting business continuity for affected customers who rely on these group structures for device management and monitoring workflows.

To mitigate this vulnerability, developers must implement strict object-level authorization checks within the GroupController logic. Every request that accesses or modifies a resource identified by an external ID must verify that the currently authenticated user is the designated owner of that specific instance. This can be achieved by maintaining explicit ownership metadata in the database and validating it during every API call related to group management. Additionally, implementing indirect object references where internal IDs are mapped through a secure lookup service rather than exposing sequential identifiers directly can reduce the attack surface for enumeration-based exploits. Regular security audits focusing on access control patterns and automated testing using tools that simulate IDOR attacks should be integrated into the development lifecycle to prevent similar flaws in future releases. This issue aligns with CWE-639, which addresses authorization bypass through direct object reference manipulation, and maps to MITRE ATT&CK techniques involving unauthorized resource access within cloud or application environments.

Responsible

VulnCheck

Reservation

10/16/2026

Disclosure

10/16/2026

Moderation

accepted

EPSS

0.00000

KEV

no

Activities

low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!