Frappe ERPNext versions 13.0.0 before 15.122.0 and 16.x before 16.50.0 have a missing authorization vulnerability in the Accounts module. This flaw allows authenticated users with the Accounts User role who can edit Bank Transactions to manipulate reconciliation states of vouchers outside their permission scope. The vulnerability arises because the system checks permissions only on the Bank Transaction, not on each voucher referenced in reconciliation requests.
Frappe ERPNext versions 12.2.0 before 15.122.0 and 16.x before 16.50.0 have a missing authorization vulnerability in the Assets module. This flaw allows authenticated users, including those with minimal privileges or portal users, to access asset details beyond their authorized scope by sending crafted requests. The vulnerability does not affect confidentiality, integrity, or availability beyond unauthorized read access to asset details.
Frappe ERPNext versions 5.0.0 before 15.121.4 and 16.x before 16.36.0 have an authorization vulnerability in the Selling module. The flaw allows authenticated users with restricted User Permissions to close or reopen Sales Orders belonging to other companies by exploiting insufficient permission checks on individual Sales Orders. The vulnerability does not affect confidentiality or availability but can lead to unauthorized modification of Sales Order status.
Frappe ERPNext versions 15.111.0 before 15.121.4 and 16.22.0 before 16.36.0 contain a missing authorization vulnerability in an Accounts module endpoint. This flaw allows authenticated users, including portal users or those without roles, to access item rows from inter-company invoices or orders belonging to other companies without proper read permission checks. The vulnerability affects endpoints that accept a caller-supplied document type and return sales and purchase invoice and order items.
Frappe ERPNext versions 5.0.0 before 15.121.4 and 16.x before 16.36.0 have an authorization vulnerability in the Buying module. The endpoint responsible for closing and reopening Purchase Orders only verifies document-type write permissions, ignoring per-document User Permissions. This allows authenticated users with Purchase Order write access to alter the status of Purchase Orders belonging to other companies by sending crafted requests.
Frappe ERPNext versions 13.0.0 before 15.122.0 and 16.x before 16.50.0 have a missing authorization vulnerability in an Accounts module endpoint. This flaw allows authenticated users with common operational roles to access Bank Transaction amounts and bank accounts of other companies by sending crafted requests that bypass proper access controls.
Frappe ERPNext versions 10.1.41 before 15.122.0 and 16.x before 16.50.0 have a missing authorization vulnerability in the Manufacturing module. This flaw allows authenticated users with permission to create a BOM Update Log to replace one Bill of Materials (BOM) with another across all assemblies site-wide without proper authorization checks. The vulnerability can lead to unauthorized modification of BOMs, impacting data integrity.
Frappe ERPNext versions 7.1.0 before 15.121.0 and 16.x before 16.34.0 have a missing authorization vulnerability in the Projects module. This flaw allows any authenticated user, even those without assigned roles, to access Timesheet data across the organization without proper access restrictions. The vulnerability exposes work and billing details that should be limited to authorized personnel.
pypdf versions before 7.0.0 have a resource exhaustion vulnerability where crafted PDF cross-reference streams cause excessive memory usage. Attackers can create PDFs with cross-reference stream offsets all pointing to a single large object, leading to memory exhaustion during parsing.
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.