CVE-2022-40816

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.

Category

6.5
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.14%
Vendor Advisory zammad.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://zammad.com/de/advisories/zaa-2022-09 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-40816?
CVE-2022-40816 has been scored as a medium severity vulnerability.
How to fix CVE-2022-40816?
To fix CVE-2022-40816, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-40816 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-40816 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.