Skip to content

Broken Object Level Authorization in Project Mutation APIs

High
drfarrell published GHSA-82m4-w39c-pgq6 Dec 14, 2025

Package

No package listed

Affected versions

< 2025-12-14

Patched versions

>= 2025-12-14

Description

Impact

A Broken Object Level Authorization (BOLA/IDOR) vulnerability allowed any authenticated user to perform unauthorized actions on projects they do not own, including:

  • Deleting other users' projects
  • Updating project metadata for other users' projects
  • Adding/removing tags on projects belonging to other users

Any authenticated user could exploit this by simply providing a valid project ID to the affected API endpoints. This affects all users of Onlook's web application.

Severity: High - Authenticated attackers could delete or modify any project in the system.

Patches

This vulnerability has been patched in commit 6138b0cb2199d042236b3cc11964a35a5744ec7c (PR #3062).

Users of the hosted Onlook service are automatically protected. Self-hosted users should pull the latest changes from the main branch.

Workarounds

There are no workarounds. Users must upgrade to a patched version.

References

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

CVE ID

CVE-2025-63783

Weaknesses

Authorization Bypass Through User-Controlled Key

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Learn more on MITRE.

Credits