Caycon

BookStack before 26.09.3 contains a missing authorization vulnerability in ImageController::checkImagePermission() that allows authenticated non-admin users to bypass page-level content restrictions for images whose owning page has been moved to the recycle bin, because the permission check relies on Page::getPage() which returns null for soft-deleted pages and silently skips the PageView check. Attackers can enumerate sequential image IDs via GET /images/edit/{id} to disclose metadata of restricted images, and users with image-update-all/image-delete-all privileges can rename, replace, or permanently delete images belonging to content they cannot view, persisting the damage even after the page is restored.

ToolJet before 3.21.94, fixed in commit e5f387a, contains an authorization bypass vulnerability in the app environments init endpoint that allows authenticated users to read app version metadata belonging to other workspaces. Attackers can send GET requests to /api/app-environments/init with an editing version id from another workspace to retrieve the version name, description, status, current environment ID, and app ID, because the lookup is not scoped to the caller's organization.

An input-validation issue exists where the functions `NewHandleWithNoSecrets()` and `ReadWithNoSecrets()` skip the structural `Validate()` step before constructing a keyset.Handle. This allows malformed public or no-secret keysets that violate internal invariants to be accepted. An attacker can provide a malformed keyset, such as one containing an enabled public key without a valid primary key or a DESTROYED key lacking `KeyData`. This leads to inconsistent downstream validation, as functions like `JWKSetFromPublicKeysetHandle()` may process the invalid handle and produce a JWK set, potentially misleading applications that assume successful handle construction ensures keyset integrity.

An authorization bypass exists in the 'POST /api/v2/resources/export' endpoint. Authenticated users can disclose TooljetDB table schemas across workspace boundaries or export app definitions by bypassing granular permission gates. This is achieved by providing a specific `organization id` parameter in the request body to access schemas from other workspaces or to export restricted app definitions within their own workspace.

Authenticated workspace members can perform unauthorized document store operations due to missing authorization on mutation endpoints. Users with view-level permissions can send direct HTTP requests to the 'upsert' and 'refresh' document store routes. This allows them to trigger document ingestion, refresh vector database contents, consume embedding API credits, and modify knowledge bases utilized by downstream chatflows.

An insecure direct object reference (IDOR) occurs in the OpenAI Assistants integration. This issue allows authenticated attackers to access credentials from other workspaces by providing an arbitrary credential UUID to Assistants endpoints, as the system fails to verify workspace ownership. By exploiting the missing workspace-scoped authorization check in the credential lookup logic, attackers can enumerate assistant metadata across workspaces, retrieve listings for files and vector stores, and upload files into victim workspaces.

An authentication bypass exists due to prefix-based whitelist matching in the authentication middleware located in `packages/server/src/utils/constants.ts`. Unauthenticated attackers can send a POST request to the 'oauth2-credential refresh' endpoint with a trailing credential identifier to bypass authentication and authorization checks. This allows unauthorized OAuth token rotation for credentials in any workspace, which may disrupt dependent OAuth integrations.

An authorization bypass exists in the `BackupRestoreController` due to a PHP operator precedence flaw in the permission check expression. This allows authenticated users without administrative privileges to bypass access controls and perform restricted actions, including creating, downloading, and restoring backups.

An issue in the `FileManagerController` allows authenticated attackers with the `file manager mkfile` capability to achieve remote code execution. This is possible due to missing file extension validation in the `create file()` and `save()` functions, enabling the creation of arbitrary PHP files within the web-accessible `FILES DIR` directory. Execution is triggered by requesting the created file over HTTP.