# CVE-2025-30369: Zulip allows the deletion of Custom profile fields by administrators of a different organization

> Administrators of one organization can delete custom profile fields belonging to a different organization due to missing ownership checks.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2025
- **Updated:** 31 Mar 2025
- **Also known as:** GHSA-fcgx-q63f-7gw4

## What is CVE-2025-30369?

CVE-2025-30369 is a low-severity missing authorization vulnerability in zulip, published on 31 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Zulip is an open-source team collaboration tool. The API for deleting an organization custom profile field 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, an administrator of any organization was incorrectly allowed to delete custom profile fields belonging to a different organization. This is fixed in Zulip Server 10.1.

Weakness: CWE-566 (Authorization Bypass Through User-Controlled SQL Primary Key)

## Which versions are affected by CVE-2025-30369?

It affects 1 product.


Products: Zulip Zulip Server.

## How do I fix CVE-2025-30369?

No fix has been published for CVE-2025-30369 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-30369 being exploited?

There is no known exploitation of CVE-2025-30369 in the wild and no public exploit code.

## Other vulnerabilities in zulip

- [CVE-2019-18933](https://insights.sbomify.com/CVE-2019-18933/): Information disclosure in n/a (critical 9.8)
- [CVE-2020-15070](https://insights.sbomify.com/CVE-2020-15070/): Code injection in n/a (high 8.8)
- [CVE-2017-0910](https://insights.sbomify.com/CVE-2017-0910/): Missing authorization in Zulip Server (high 8.8)
- [CVE-2025-31478](https://insights.sbomify.com/CVE-2025-31478/): Zulip Authentication Backend Configuration Bypass (high 8.2)
- [CVE-2023-33186](https://insights.sbomify.com/CVE-2023-33186/): Cross-site scripting vulnerability in Zulip Server development branch via topic tooltip (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30369 and fix it if it is affected.

What it is: CVE-2025-30369 is a low-severity missing authorization vulnerability in zulip, published on 31 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30369 in the wild and no public exploit code.

Affected product: zulip. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-30369/ (Markdown: https://insights.sbomify.com/CVE-2025-30369/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-30369
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-30369
- OSV: https://osv.dev/vulnerability/CVE-2025-30369

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-30369/
Summaries are generated and may contain mistakes; the official description above is the record.