CVE-2022-40816 - CVE House
Back to Database
Status published Unknown CVE-2022-40816

Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset...

Vulnerability Description

Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset handling mechanism has logic to ensure that customer users are not able to see personal information of other users. This logic was not effective when used through a web socket connection, so that a logged-in attacker would be able to fetch personal data of other users by querying the Zammad API. This issue is fixed in , 5.2.2.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2022-40816

Credits & Attribution

No credits recorded in the NVD database.

References

More from zammad

View All →
CVE-2022-48023
Insufficient privilege verification in Zammad v5.3.0 allows an authenticated attacker...
Medium 4.3
CVE-2022-48022
An issue in the component /api/v1/mentions of Zammad v5.3.0 allows...
Unknown 0
CVE-2022-48021
A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary...
Unknown 0
CVE-2022-40817
Zammad 5.2.1 has a fine-grained permission model that allows to...
Unknown 0
CVE-2022-35490
Zammad 5.2.0 is vulnerable to privilege escalation. Zammad has a...
Critical 9.8

Affected Vendor

Affected Software

zammad
Vulnerable Versions:
5.2.0

Timeline

Official Publish: September 27th, 2022
Last Modified: May 21st, 2025
Added to House: July 21st, 2026

CVSS Vectors

No vector data available

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.