Frappe ERPNext versions 4.3.0 before 15.121.6 and 16.x before 16.37.0 have an SQL injection vulnerability in an endpoint of the Selling and Buying modules. This flaw allows any authenticated user, including portal users without roles, to send crafted requests that override early validation and reach the database unvalidated. Exploitation can lead to extraction of sensitive data such as active session information and account takeover, including administrator accounts.
Frappe ERPNext versions 13.0.0 before 15.124.0 and 16.x before 16.52.0 have an authorization vulnerability in the Accounts module. Authenticated users with an Accounts role can access metadata of Payment Entries they should not have permission to see due to insufficient permission checks on an endpoint. This vulnerability allows exposure of restricted Payment Entry metadata without proper read permission validation.
Frappe ERPNext versions 15.0.0 before 15.124.0 and 16.x before 16.52.0 have a missing authorization vulnerability in the Assets module. Authenticated users can access depreciation schedules of assets belonging to other companies without proper read permission checks. This exposure allows disclosure of sensitive financial details such as purchase value and depreciation entries.
Frappe ERPNext versions 11.0.0-beta before 15.122.0 and 16.x before 16.34.0 have a missing authorization vulnerability in an Accounts module endpoint. This flaw allows authenticated attackers to query subscription plans linked to invoices without proper read permission checks. Attackers can craft requests naming invoices outside their access scope to determine subscription membership and view billed plans. The vulnerability has a CVSS score of 5.0, indicating medium severity.
Frappe ERPNext versions 14.0.0 before 15.121.0 and 16.x before 16.34.0 have a missing authorization vulnerability in a Utilities module endpoint. This flaw allows any authenticated user, including portal users without roles, to retry failed bulk transactions without proper role checks. Exploitation can remove failed transactions from the normal recovery process and increase background job load on the system.
pypdf versions 2.4.2 up to but not including 7.0.0 contain a resource exhaustion vulnerability in their handling of XFA forms. This flaw allows attackers to craft PDF files with many small XFA form fields that cause excessive memory consumption when loaded, leading to denial of service.
Frappe Framework versions before 15.120.1 and 16.x before 16.33.1 have a path traversal vulnerability in their file attachment handling. This flaw allows authenticated users with minimal privileges to read arbitrary files on the server outside the intended application boundaries. The vulnerability does not require write permissions and can lead to exposure of sensitive server files.
Frappe versions from 8.8.0 up to but not including 16.30.0 have an insecure direct object reference vulnerability in the SMS Settings get_contact_number API. This flaw allows attackers with some privileges to retrieve phone numbers of arbitrary Contact records without proper permission checks, exposing personally identifiable information (PII). The vulnerability arises from an uncorrelated EXISTS subquery used in the endpoint.
pypdf versions 3.7.1 up to but not including 7.0.0 contain an information disclosure vulnerability. This flaw allows attackers to guess placeholders in encrypted templated PDF documents by analyzing file identifiers. An attacker with access to a document sharing the same template and other documents' file identifiers can recover sensitive placeholder contents from encrypted PDFs.
Heym versions before 0.0.148 contain a vulnerability where Playwright navigate-step URLs are passed to page.goto() without validating the URL scheme. This allows a signed-in user with workflow execution permissions to navigate to file:// URLs and read sensitive files such as Kubernetes ServiceAccount tokens or Docker secrets from the backend container.
AzuraCast versions prior to 0.24.1 have an improper authorization vulnerability in the /api/station/{station_id}/profile/edit endpoint. This flaw allows authenticated station users with Manage Station Profile permission—but without Manage Station Broadcasting permission—to read and modify Icecast/Shoutcast passwords. Attackers can retrieve admin, source, relay, and streamer passwords or overwrite them, potentially locking out legitimate operators.
AzuraCast versions prior to 0.24.1 contain a vulnerability where backslashes in Liquidsoap annotation values are not properly escaped. This flaw allows media managers to break out of quoted annotation strings by crafting an ID3 title ending with a backslash, enabling injection of a process: protocol URI. Successful exploitation results in OS command execution within the Liquidsoap container during media playback.
Coder versions 2.6.0 before 2.29.21, 2.30.0 before 2.34.10, 2.35.0 before 2.35.8, 2.36.0 before 2.36.5, and 2.37.0 before 2.37.1 contain a denial of service vulnerability in the workspace agent dRPC API. The vulnerability arises because handlers dereference unset request sub-messages and unconfigured Tailnet providers without recovering from panics. An attacker with a workspace agent token can exploit this by sending specific malformed messages to repeatedly crash the coderd process.
rclone versions before 1.76.0 have a vulnerability in the swift, netstorage, and seafile backends where credentials can be leaked due to following HTTP redirects with Go's default policy. This causes authentication headers, passwords, or API tokens to be sent on redirects that downgrade from HTTPS to HTTP or cross-host redirects, potentially exposing sensitive credentials to attackers who can observe or receive these redirects.
Rclone versions from 1.51.0 up to but not including 1.76.0 have an authentication bypass vulnerability in the serve sftp --auth-proxy feature. The vulnerability arises because the cache key used for authentication does not include the authentication method, allowing attackers who know a victim's base64 public key to reuse cached authentication entries from the same client IP. This enables unauthorized read-write access to the virtual file system (VFS).
Coder versions 2.32.0 before 2.34.17, 2.35.0 before 2.36.12, 2.37.0 before 2.37.9, and 2.38.0 before 2.38.5 contain a symlink-following vulnerability in the Coder Agents read_skill_file tool. This flaw allows attackers who place a malicious skill with a symlinked supporting file in a victim's workspace to leak files outside the intended skill directory into the model context and chat history. The vulnerability arises because the tool validates skill file paths lexically but follows symlinks outside the skill directory. The CVSS score is 3.1, indicating low severity. No known exploits in the wild have been reported, and no patch links are provided in the data.
Coder versions prior to 2.29.26, 2.34.18, 2.37.10, and 2.38.6 contain a cross-site request forgery (CSRF) vulnerability. This occurs because CSRF exemption patterns are matched as unanchored regular expressions, allowing some API routes to bypass CSRF token and same-origin checks. An attacker controlling a same-site page can trick signed-in users' browsers into sending forged POST requests that may recreate development containers or add users with specific names to organizations.
AzuraCast versions from 0.19.0 up to but not including 0.24.1 have an improper authorization vulnerability. This flaw allows users with station media rights to add tracks to playlists of other stations by manipulating playlist IDs in the single-file edit endpoint. Exploitation can result in unauthorized injection of entries into other stations' AutoDJ rotations and public now-playing metadata, potentially causing playback failures.
rclone versions from 1.59.0 up to but not including 1.76.0 contain a vulnerability in the local backend's setXattr function. This flaw allows attackers to escape confinement by writing user.* extended attributes outside the intended destination root directory via a specially crafted symlink. Exploitation requires the attacker to plant a symlink pointing to an external directory with existing child files and use specific rclone operations (--links --metadata) to set extended attributes on those external files.
rclone versions from 1.67.0 up to but not including 1.76.0 have a vulnerability in the Ulozto backend where authentication tokens (X-Auth-Token and X-User-Token) are sent to unintended hosts during HTTP redirects. This occurs because the downloads use the authenticated f.rest client instead of the f.cdn client, potentially exposing long-lived API keys and session tokens to attackers who can observe or redirect CDN traffic.