Live › vulnerability › CVE-2026-108046
Alosuite does not check authorization when it processes object identifiers in the /Companies/Edit/{id} endpoint. An unauthenticated remote attacker can change the identifier, enumerate valid ones, and read company and user data they should not see.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 13:20 UTC. All times on this page are UTC.
Any deployment of Alosuite that exposes the /Companies/Edit/{id} endpoint to the network is potentially exposed, since the sources describe no authentication requirement. Teams that do not run Alosuite can skip it. The sources do not name affected versions.
No product ranges from the sources yet.
Unknown from the sources.
No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Direct Object Reference (IDOR) vulnerability in Alosuite due to insufficient authorization checks when processing object identifiers. By modifying the identifier provided to the ‘/Companies/Edit/{id}’ endpoint, an attacker can access information associated with other companies or users without the appropriate authorization. The vulnerability allows unauthenticated remote attackers to enumerate valid object identifiers and retrieve information that should be restricted to authorized users, resulting in the unauthorized disclosure of application data.
This page as .md · .json · in your agent: get_signal("CVE-2026-108046")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.