Alham-Rizvi

SiYuan before v3.8.2 contains a stored cross-site scripting vulnerability in the search asset preview feature that fails to escape indexed asset content before inserting it into the DOM using innerHTML. Attackers who can place crafted text assets in a workspace can execute JavaScript in the SiYuan origin when victims preview the assets, enabling authenticated API requests and workspace manipulation.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.8.2 **Description** An information disclosure issue exists in the 'getAttributeViewKeysByID' endpoint. This allows users with publish reader permissions to enumerate private attribute view key definitions without the system verifying the visibility of the parent database. An attacker can use this endpoint to retrieve complete key schemas, including sensitive field names and relation definitions, from hidden databases. **Recommendations** Update SiYuan to version 3.8.2 or later. As a temporary mitigation, restrict access to the 'getAttributeViewKeysByID' endpoint.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.8.2 **Description** Insufficient filtering of private attribute-view cell values occurs in the 'getAttributeViewKeys' endpoint. This allows publish readers to retrieve hidden `KeyValues` payloads from rows linked to documents they cannot access, leading to unauthorized exposure of private database contents. **Recommendations** Update to version 3.8.2 or later.

**Name of the Vulnerable Software and Affected Versions** Grav Admin versions prior to 2.0.20 **Description** Insufficient sanitization of output from the `marked.parse()` function before it is injected into the Document Object Model (DOM) via Svelte's `{@html}` directive within the MarkdownEditor and MarkdownModal components. This allows attackers to inject `javascript:` URI schemes into plugin or theme changelogs, leading to arbitrary code execution in authenticated administrator sessions. **Recommendations** Update Grav Admin to version 2.0.20 or later.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.8.2 **Description** An information disclosure issue exists in the reader-accessible POST '/api/transactions/undoState' endpoint. The endpoint returns the `peekMutatedRootIDs` list from the global undo-log stack for a caller-supplied `root ID` without applying publish-access visibility filtering. An authenticated reader who knows the root ID of a visible document can obtain the internal root IDs of other documents, including private or unpublished ones, that were modified in the same cross-document transaction. This discloses internal identifiers and cross-document relationships, although document body contents are not directly exposed. **Recommendations** Update to version 3.8.2.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.8.2 **Description** An authorization bypass exists in the '/api/file/getFile' endpoint. Users with a reader role can retrieve files from notebooks configured as `Visible:false` if they know the hidden notebook identifier and the file path. This allows unauthorized access to private workspace files, including internal configuration and notebook metadata. **Recommendations** Update to version 3.8.2 or later. Restrict access to the '/api/file/getFile' endpoint to minimize the risk of unauthorized file retrieval.

**Name of the Vulnerable Software and Affected Versions** Grav Admin (getgrav/grav-plugin-admin2) versions prior to 2.0.21 **Description** A stored cross-site scripting issue exists in the `tHtml()` function (src/lib/stores/i18n.svelte.ts), which inserts untrusted parameters like usernames into translation templates before parsing them as markdown. Because the server-side validation function `isValidUsername()` does not block characters such as <, >, ", or ', an attacker can register a username containing an HTML payload. This payload executes in the authenticated session of an administrator when they view UI elements that render the username via `tHtml()`, such as the 'page is locked' editor notice or the two-factor force-disable confirmation prompt. **Recommendations** Update Grav Admin (getgrav/grav-plugin-admin2) to version 2.0.21.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.8.2 **Description** The publish-service Basic Auth handler contains an unbounded session creation issue. Authenticated attackers can repeatedly authenticate using valid credentials to generate persistent session entries that lack expiry or capacity limits. This leads to continuous process memory growth, resulting in a denial of service. **Recommendations** Update to version 3.8.2 or later.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.8.2 **Description** The request-concurrency middleware contains an unbounded resource consumption issue where mutex entries are retained for every unique request path without an eviction mechanism. Unauthenticated attackers can exploit this by sending a large number of unique request paths, leading to a permanent increase in process memory and synchronization overhead, which degrades system availability. **Recommendations** Update to version 3.8.2 or later.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.8.1 **Description** In publish mode, the software fails to filter invisible-tier content from SQL embed blocks, attribute-view keys, and attribute-view backlinks. This allows anonymous readers to enumerate content that has been marked as unlisted by the administrator. **Recommendations** Update to version 3.8.1 or later.

**Name of the Vulnerable Software and Affected Versions** SiYuan version 3.8.0 **Description** An authenticated attacker can exploit a path traversal and sensitive file exposure issue through the `RenderTemplate()` function. This is reachable via the 'POST /api/template/render' endpoint. While the system restricts paths to the workspace directory using `util.IsAbsPathInWorkspace`, it fails to apply a sensitive-path exclusion blocklist. This allows the unauthorized reading of sensitive workspace files, such as `conf/conf.json`, which stores the API token and cookie signing key. **Recommendations** Update SiYuan to version 3.8.1.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.8.1 **Description** An issue exists in `kernel/server/serve.go` where the `IsForbiddenAbsPath` guard is not applied to the '/history/*path' and '/repo/diff/*path' endpoints. Although these endpoints require administrator authentication, they construct file paths independently. This allows an authenticated administrator to retrieve historical snapshots of sensitive files, such as `data/.siyuan/publishAccess.json`, which contains plaintext publish-mode passwords, and files located under `data/templates/`. **Recommendations** Update SiYuan to version 3.8.1 or later.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.8.1 **Description** Improper escaping of block name, alias, and memo fields occurs within the hint, backlink, and breadcrumb rendering functions. This allows an attacker to inject HTML or script tags into a block's name, which are then executed when another user views documents that reference or display that block. **Recommendations** Update to version 3.8.1 or later.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.8.1 **Description** A stored cross-site scripting issue exists in the `confirmDialog()` function. This occurs because unescaped package names and notebook names are interpolated directly into innerHTML assignments. An attacker can submit malicious bazaar packages containing HTML or script payloads in the name field, which then execute in the browser of a user when they uninstall packages or unlock encrypted notebooks. **Recommendations** Update to version 3.8.1 or later.

**Name of the Vulnerable Software and Affected Versions** getgrav/grav-plugin-api versions prior to 1.0.18 **Description** The getgrav/grav-plugin-api plugin fails to enforce API-key scope within the `requireNotSuperTarget()` function located in `UsersController.php` across seven sensitive user-management endpoints. The system incorrectly uses `isSuperAdmin()` to check the acting account instead of verifying if the specific API key possesses super authority through `isSuperWithinScope()`. This allows an API key with limited scope, if it belongs to a super-admin account, to perform unauthorized actions against other super-admin accounts, such as disabling two-factor authentication (2FA), deleting avatars, creating new API keys under their identity, or deleting existing API keys. **Recommendations** Update getgrav/grav-plugin-api to version 1.0.18 or later.

**Name of the Vulnerable Software and Affected Versions** Grav API plugin (getgrav/grav-plugin-api) versions prior to 1.0.18 **Description** The `injectSecurityTab()` function within the `BlueprintController` fails to apply the API-key scope cap when determining if a page's security or permissions blueprint section is editable. The function executes `isSuperAdmin()` and `hasPermission()` checks without a request parameter, which prevents the enforcement of `scopeAllows()`. Consequently, a user with a scoped API key can view and potentially modify page permission fields that exceed the permissions granted to that key. **Recommendations** Update Grav API plugin (getgrav/grav-plugin-api) to version 1.0.18 or later.

**Name of the Vulnerable Software and Affected Versions** Grav CMS versions prior to 2.0.16 **Description** An origin validation bypass exists in the `Uri::referrer()` and `Pages::referrerRoute()` methods. The issue occurs because the Referer header is validated using an unanchored string prefix match via `str starts with($referrer, $base)` without a trailing delimiter. This allows an attacker controlling a domain that starts with the victim site's origin to send a request that is incorrectly treated as same-origin, bypassing the origin check. **Recommendations** Update Grav CMS to version 2.0.16 or later.

**Name of the Vulnerable Software and Affected Versions** Grav CMS versions prior to 2.0.16 **Description** Sandboxed Twig renders fail to filter system, site, and theme configuration arrays. This allows users with page-content edit access to read sensitive configuration values, such as cache credentials, by using dot notation in Twig templates. This technique bypasses the `config denied paths` restrictions. **Recommendations** Update Grav CMS to version 2.0.16 or later.

**Name of the Vulnerable Software and Affected Versions** Grav versions prior to 2.0.16 **Description** Sandboxed Twig templates can access sensitive User fields because the allow-listed `offsetGet()` and `offsetexists()` methods lack proper field filtering. Users with page-edit permissions can utilize the `offsetGet()` function on User objects to retrieve hashed passwords and 2FA secrets, which may facilitate offline password cracking and authentication bypass. **Recommendations** Update Grav to version 2.0.16 or later.

**Name of the Vulnerable Software and Affected Versions** Grav Login plugin versions prior to 3.9.1 **Description** An issue exists where the registration endpoint allows for email address enumeration. The `register()` function in classes/Login.php triggers a specific exception, `EMAIL NOT AVAILABLE`, when a provided email address is already associated with an account, whereas other attempts allow the process to continue. Due to the absence of rate limiting on the registration endpoint, an attacker can systematically identify registered email addresses by submitting requests individually. **Recommendations** Update Grav Login plugin to version 3.9.1 or later.