Maykinmedia Open Object up to 2.5.0/3.6.1/4.0.1/4.1.0 History Detail Endpoint views.py history_detail privileges management

Summaryinfo

A vulnerability classified as problematic has been found in Maykinmedia Open Object up to 2.5.0/3.6.1/4.0.1/4.1.0. The impacted element is the function history_detail of the file src/objects/api/v2/views.py of the component History Detail Endpoint. Performing a manipulation results in privileges management. This vulnerability is cataloged as CVE-2026-82411. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Maykinmedia Open Object up to 2.5.0/3.6.1/4.0.1/4.1.0. This affects the function history_detail of the file src/objects/api/v2/views.py of the component History Detail Endpoint. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality. The summary by CVE is:

Open Object provides an API and admin interface to manage objects and object types. From 2.4.3 until 2.5.1, 3.6.2, 4.0.2, and 4.1.1, a token scoped to read one ObjectType can read the full versioned record of an object of any other ObjectType via the history-detail endpoint `GET /api/v2/objects/{uuid}/{index}`. The `history_detail` action in `src/objects/api/v2/views.py` calls `self.get_queryset()` and `get_object_or_404` directly instead of `self.get_object()`, so `check_object_permissions` and the per-object check in `ObjectTypeBasedPermission.has_object_permission` are not invoked. The queryset's `filter_for_token` applies only to the list and search actions, while `ObjectTypeBasedPermission.has_permission` allows non-create actions, leaving neither check to constrain history-detail records to the token's permitted ObjectType. The normal retrieve endpoint returns 403 for the same unauthorized object, and the sibling history action enforces the grant. Any valid non-superuser API token with a read grant on at least one ObjectType can therefore disclose another ObjectType's complete versioned object `data`, which can include citizen or case records and sensitive identifiers in government deployments. This issue is fixed in versions 2.5.1, 3.6.2, 4.0.2, and 4.1.1.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-82411 since 08/29/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

Upgrading to version 2.5.1, 3.6.2, 4.0.2 or 4.1.1 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Maykinmedia

Name

• Open Object

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5.0
• 3.6.0
• 3.6.1
• 4.0
• 4.0.0
• 4.0.1
• 4.1.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion