Odgrso

Certain endpoints fail to enforce proper permission checks, allowing authenticated attackers with low-privileged accounts to access and read financial data that exceeds their assigned role permissions.

Missing input validation in certain endpoints allows authenticated attackers to perform SQL injection. By sending specially crafted requests, an attacker can manipulate database queries to extract sensitive information from the database.

Missing input validation in certain endpoints allows authenticated attackers to perform SQL injection, which is a technique used to manipulate database queries. By sending specially crafted requests, an attacker can extract sensitive information from the database.

A stored cross-site scripting issue exists because record names are not properly neutralized when rendered on dashboards, tools, and portals. Authenticated attackers can create malicious record names to execute scripts in the browsers of other users, which may lead to data access, data modification, and token theft, particularly targeting privileged users.

Missing input validation in certain endpoints allows authenticated attackers to execute SQL injection. By sending specially crafted requests, an attacker can inject SQL into database queries to extract sensitive information from the underlying database.

Missing input validation in certain endpoints allows authenticated low-privileged attackers to execute SQL injection. By sending specially crafted requests, an attacker can inject SQL commands to extract sensitive information from the database.

Missing input validation in multiple endpoints allows authenticated attackers to perform SQL injection. By sending specially crafted requests, an attacker can manipulate database queries to extract sensitive information from the database.

A DOM-based cross-site scripting issue exists in the HTML preview, which renders execution output into an `iframe srcdoc` without the `sandbox` attribute. A sanitizer bypass allows injected scripts to execute with the same origin as the editor. This enables an account with `global:member` privileges to call authenticated APIs using the victim's session when the preview is opened.

The Token Exchange module assigns all Public API key scopes to issued JSON Web Tokens (JWTs), ignoring the actual role of the acting user. In environments where the Token Exchange feature and Public API are enabled, a low-privileged user with a valid external JWT from a trusted issuer can use the resulting access token to perform administrator-only Public API operations, including user creation, user deletion, and role escalation. Furthermore, if unverified Community Package installation is enabled, this can lead to remote code execution.

A stored DOM cross-site scripting issue exists in the Resource Locator component. The component passes the workflow-persisted `cachedResultUrl` parameter to the `window.open()` function without validating the scheme. An attacker with privileges to create or edit workflows can include a malicious scheme, such as `javascript:`, in the `cachedResultUrl` variable. When a victim opens the crafted workflow and interacts with external links, the payload executes within the victim's browser.

Mastodon is a free, open-source social network server based on ActivityPub. A flaw in the definition of the `attributionDomains` JSON-LD term makes Linked Data Signatures on the `toot:attributionDomains` property ineffective. This allows an attacker to arbitrarily modify the `attributionDomains` value of a legitimately signed Update activity and bypass signature verification, potentially leading to false attribution claims.

Name of the Vulnerable Software and Affected Versions Vite versions 6.0.0 through 6.4.1, 7.3.2, and 8.0.5 Description The Vite dev server improperly handles .map requests for optimized dependencies. It resolves file paths and calls readFile without restricting '../' segments in the URL, potentially allowing bypass of the server.fs.strict allow list and retrieval of .map files located outside the project root if they are valid source map JSON. This could expose sensitive content if the server is exposed to the network and predictable paths to .map files exist. Recommendations Update to Vite version 6.4.2 or later, 7.3.2, or 8.0.5.

Name of the Vulnerable Software and Affected Versions Vite versions 6.0.0 through 6.4.1, 7.3.2, and 8.0.5 Description Vite, a frontend tooling framework for JavaScript, had a flaw where the `server.fs` check was not enforced for the `fetchModule` method exposed in the Vite dev server’s WebSocket. If a connection to the Vite dev server’s WebSocket could be established without an Origin header, an attacker could invoke `fetchModule` via the custom WebSocket event `vite:invoke` and combine `file://...` with `?raw` (or `?inline`) to retrieve the contents of arbitrary files on the server as a JavaScript string. The access control enforced in the HTTP request path was not applied to this WebSocket-based execution path. This could allow exposure of arbitrary files on the server, including those in the development machine, CI environment, or container. Recommendations Update Vite to version 6.4.2 or later, 7.3.2, or 8.0.5.

Name of the Vulnerable Software and Affected Versions Vite versions 7.1.0 through 7.3.1 and 8.0.0 through 8.0.4 Description Vite, a frontend tooling framework for JavaScript, allows retrieval of files blocked by `server.fs.deny` (such as .env and *.crt files) with HTTP 200 responses when specific query parameters like ?raw, ?import&raw, or ?import&url&inline are appended to the request. This occurs when the Vite dev server is exposed to the network and sensitive files are both allowed by `server.fs.allow` and denied by `server.fs.deny`. Recommendations Vite versions 7.1.0 through 7.3.1 should be updated to version 7.3.2 or later. Vite versions 8.0.0 through 8.0.4 should be updated to version 8.0.5 or later.

Name of the Vulnerable Software and Affected Versions Directus (affected versions not specified) Description When `GRAPHQL INTROSPECTION=false` is configured, Directus blocks standard GraphQL introspection queries but the `/graphql/system` endpoint's `server specs graphql` resolver returns an equivalent SDL representation of the schema. This bypasses introspection controls, exposing schema structure (collection names, field names, types, and relationships) to unauthenticated users at the public permission level, and to authenticated users at their permitted permission level. Administrators setting `GRAPHQL INTROSPECTION=false` had a false sense of security, as schema information remained accessible via the SDL endpoint. 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 Directus versions prior to 11.17.0 Description The Directus file management API contains a broken access control issue that allows authenticated users to overwrite files belonging to other users by manipulating the `filename disk` parameter in the `PATCH /files/{id}` endpoint. By setting this value to match the storage path of another user's file, an attacker can overwrite the file's content and manipulate metadata fields like `uploaded by` to hide the tampering. This can lead to unauthorized file overwrites, potential remote code execution if the storage backend is shared with the extensions location, and data integrity compromise. Recommendations Update to version 11.17.0 or later.

Name of the Vulnerable Software and Affected Versions Directus versions prior to 11.16.0 Description A Server-Side Request Forgery (SSRF) protection bypass exists in Directus. The IP address validation used to block requests to local and private networks could be circumvented using IPv4-Mapped IPv6 address notation. The validation logic failed to normalize IPv4-Mapped IPv6 addresses before checking them against the deny-list, allowing an attacker to bypass the restriction. This could allow an authenticated user (or an unauthenticated user if public file-import permissions are enabled) to perform SSRF attacks against internal services or cloud instance metadata endpoints. Recommendations Update to version 11.16.0 or later.

An issue exists where attachments from web-public streams remain accessible anonymously even after spectator access is disabled via `enable spectator access` or `WEB PUBLIC STREAMS ENABLED`. Additionally, the '/users/me/<stream id>/topics' endpoint remains reachable anonymously, allowing unauthorized retrieval of topic history for web-public streams.

Connect-CMS is a content management system. An authenticated user may be able to execute arbitrary code in the Code Study Plugin. If exploited, this could lead to code execution on the server or information disclosure.

A Stored Cross-site Scripting (XSS) issue exists in the file field of the Form Plugin. If exploited, arbitrary script could run in an administrator's browser, potentially leading to unauthorized actions or information theft.