Security readout for executives and security teams
Plain-English summary
Zammad 5.2.1 could let a logged-in user access personal information belonging to other users. The issue affects confidentiality, not system takeover, data modification, or outage. The public record says it is fixed in Zammad 5.2.2.
Executive priority
Treat this as a moderate confidentiality issue. It deserves timely remediation on customer-facing or sensitive helpdesk systems, especially where many external users have accounts.
Technical view
This is an incorrect access control flaw in Zammad asset handling. Controls intended to prevent customer users from seeing other users' personal data were ineffective through a web socket connection, enabling authenticated API access to personal data. CVSS 3.1 is 6.5: network reachable, low complexity, privileges required, no user interaction, high confidentiality impact.
Likely exposure
Exposure is most relevant for organizations running Zammad 5.2.1 where authenticated customer or user accounts can reach the Zammad API and web socket functionality.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not marked KEV. Exploitation requires a logged-in attacker, but CVSS indicates low attack complexity and no user interaction once authenticated.
Researcher notes
Evidence is limited but consistent: the flaw is CWE-863 incorrect authorization in Zammad 5.2.1 and fixed in 5.2.2. The source data does not identify broader affected version ranges, exploit publication, or non-upgrade mitigations.
Mitigation direction
- Upgrade affected Zammad 5.2.1 deployments to 5.2.2 or later.
- Review the Zammad advisory for vendor-specific upgrade guidance.
- Prioritize instances containing sensitive customer or employee personal data.
- Monitor for unusual authenticated API access involving user or asset data.
Validation and detection
- Inventory Zammad deployments and flag any running version 5.2.1.
- Confirm upgraded systems report Zammad 5.2.2 or later.
- Review logs for suspicious authenticated API or web socket access to personal data.
- Validate customer users cannot access other users' personal information after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-40816 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://zammad.com/de/advisories/zaa-2022-09CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.