Hypnguyen1209

**Name of the Vulnerable Software and Affected Versions** Spring Cloud Function versions 5.0.0 through 5.0.3 Spring Cloud Function versions 4.3.0 through 4.3.4 Spring Cloud Function versions 4.2.0 through 4.2.7 **Description** An issue exists that may allow arbitrary file read and Server-Side Request Forgery (SSRF), a technique where an attacker induces a server-side application to make requests to an unintended location. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Spring Cloud Config versions 5.0.0 through 5.0.4 Spring Cloud Config versions 4.3.0 through 4.3.4 Spring Cloud Config versions 4.0.0 through 4.2.8 Spring Cloud Config versions 3.1.14 and earlier **Description** The native environment repository in Spring Cloud Config Server allows the exposure of configuration files located outside of the configured repository path. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Winter CMS versions prior to 1.2.13 **Description** Authenticated backend users can disclose arbitrary files readable by the PHP process by injecting `@import (inline)` directives into LESS source that the backend compiles. This occurs because the LESS parser was instantiated without a safe import resolver, allowing absolute paths and directory traversal via `..` to access files outside the intended directory, such as the `.env` file containing the `APP KEY` and database credentials. The issue is reachable through four entry points: - Brand Settings `custom css` field - Editor Settings `html custom styles` field - Mail Brand Settings colour-picker fields - Theme `.less`, `.sass`, and `.scss` assets Exploitation requires a backend account with specific permissions, which are assigned by default to the Developer role. **Recommendations** Update Winter CMS to version 1.2.13. As a temporary mitigation, remove the `cms.manage assets` permission from any non-trusted roles and clear all values from the Brand Settings `custom css` and Editor Settings `html custom styles` fields.

**Name of the Vulnerable Software and Affected Versions** Budibase versions prior to 3.40.0 **Description** Authenticated builders can upload files containing traversal sequences in S3 object keys because the software fails to properly sanitize them. These sequences are preserved during workspace export, allowing attackers to use filenames with `..` segments to escape the temporary directory and write arbitrary content to any path accessible by the Budibase process. **Recommendations** Update to version 3.40.0 or later.

**Name of the Vulnerable Software and Affected Versions** Budibase versions prior to 3.40.0 **Description** An unauthenticated SQL injection exists in webhook-triggered automations that utilize `EXECUTE QUERY` steps. An attacker can send a POST request containing malicious JSON to the webhook trigger endpoint to inject SQL payloads. These payloads execute using the database credentials configured by the builder, which may allow for data exfiltration, modification, and the establishment of persistence within connected datasources, such as Snowflake. **Recommendations** Update Budibase to version 3.40.0 or later.

**Name of the Vulnerable Software and Affected Versions** SiYuan desktop versions prior to 3.7.2 **Description** A reflected cross-site scripting issue exists in the bazaar plugin readme handler. An attacker can execute arbitrary code by crafting a malicious `siyuan://` deep link. By injecting HTML payloads through the plugin name parameter, the attacker can achieve full Node.js access due to the use of `insertAdjacentHTML` rendering within an insecurely configured Electron renderer. **Recommendations** Update SiYuan desktop to version 3.7.2 or later.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.7.2 **Description** Stored cross-site scripting is possible due to improper escaping of the `title-img` Individual Attribute List value during the rendering of Gallery and Kanban cover images. This occurs via unescaped style attribute interpolation. Users with editor permissions can inject `onload` handlers to execute arbitrary code within the Electron renderer, which grants full Node.js access when a victim opens the affected documents. **Recommendations** Update to version 3.7.2 or later.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.7.2 **Description** A missing authorization issue exists in the 'POST /mcp' kernel endpoint, which is only protected by a general authentication check `model.CheckAuth()` without enforcing admin roles or read-only restrictions. This flaw exposes 31 MCP tools, including a file tool capable of listing, reading, writing, deleting, renaming, and copying files across the entire workspace. If the Publish server is configured in anonymous mode (`Conf.Publish.Enable=true` and `Conf.Publish.Auth.Enable=false`), the reverse proxy attaches an anonymous RoleReader JWT to requests, enabling unauthenticated remote attackers to access the endpoint. An attacker can extract `accessAuthCode`, `api.token`, and `cookieKey` in plaintext from `conf/conf.json`, write arbitrary files, and install a malicious plugin in `data/plugins/` that executes with `nodeIntegration:true` and no `contextIsolation` upon the next desktop launch, resulting in full administrator takeover. **Recommendations** Update to version 3.7.2 or later. As a temporary mitigation, disable the Publish server anonymous mode by setting `Conf.Publish.Enable=false` or `Conf.Publish.Auth.Enable=true`.

**Name of the Vulnerable Software and Affected Versions** Budibase versions prior to 3.40.0 **Description** A cross-site request forgery (CSRF) issue exists in the 'chat-link handoff' endpoint. This allows an attacker to bind an external chat identity to a victim's account by crafting a phishing page that automatically submits a POST request containing a leaked confirmation token. Successful exploitation enables the attacker to impersonate the victim within agent operations and inherit their permissions. **Recommendations** Update to version 3.40.0 or later.