CVE-2025-63783: onlook · n/a
Affects onlookSource CVE Database V5
Not known to be exploited · CVSS 7.6 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmonlookpkg:npm/onlookOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-63783, organizations should implement strict object-level authorization checks within the Onlook application APIs, ensuring that any request to modify, delete, or tag a project verifies the authenticated user's ownership or membership of the project. Until an official patch is released, administrators should consider restricting access to the affected APIs to trusted users only and monitor API logs for suspicious activity involving project IDs not owned by the requester. Employing Web Application Firewalls (WAFs) with custom rules to detect anomalous API requests referencing unauthorized project IDs can provide additional protection. Organizations should also enforce the principle of least privilege, limiting user permissions to only necessary projects. Regular security audits and penetration testing focused on authorization controls can help identify similar weaknesses. Finally, maintain close communication with the Onlook vendor for updates and apply patches immediately upon release.
Description
A Broken Object Level Authorization (BOLA) vulnerability was discovered in the tRPC project mutation APIs (update, delete, add/remove tag) of the Onlook web application 0.2.32. The vulnerability exists because the API fails to verify the ownership or membership of the currently authenticated user for the requested project ID. An authenticated attacker can send a malicious request containing another user's project ID to unlawfully modify, delete, or manipulate tags on that project, which can severely compromise data integrity and availability.