CVE-2025-30368
Zulip 10.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:NSummary
CVE-2025-30368 is a low-severity Authorization Bypass Through User-Controlled SQL Primary Key (CWE-566) vulnerability in Zulip Zulip. Its CVSS base score is 2.7 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 25th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-8837
Vulnerability Data
Zulip is an open-source team collaboration tool. The API for deleting an organization export is supposed to be restricted to organization administrators, but its handler failed to check that the field belongs to the same organization as the user. Therefore,…
more
an administrator of any organization was incorrectly allowed to delete an export of a different organization. This is fixed in Zulip Server 10.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 requires enforcement of authorizations on every access request, which directly stops a caller from reaching unauthorized rows via a supplied primary key.
AC-24 mandates that access-control decisions be applied to each request, preventing blind trust of a user-supplied primary key.
Least privilege reduces the set of records an account can touch, limiting blast radius even if the key check is missing.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing policy-based authorization and least privilege directly prevents actor-controlled primary-key access to unauthorized records.
Secure SDLC practices include input validation, parameterized queries, and authorization checks that eliminate this class of SQL primary-key bypass.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect missing authorization checks and unsafe SQL construction before release.
Enforcing information-access restrictions prevents direct use of user-supplied primary keys to bypass authorization checks.
Access-control policy sets the governance expectation that all data access must be authorized, indirectly supporting prevention of CWE-566.
Defining application security requirements includes mandatory server-side authorization and parameterized queries that block this weakness.
Secure architecture principles require least-privilege data access and input validation, directly mitigating the described authorization bypass.
Secure-coding standards mandate parameterized queries and server-side authorization, eliminating the root cause of CWE-566.