Security advisory
An issue was discovered in Zammad 3.0 through 3.2. It allows for users to view ticket customer details associated with specific customers. However, the application does not properly implement access controls related to this functionality. As such, users of one company are able to access ticket data from other companies. Due to the multi-tenant nature of this application, users who can access ticket details from one organization to the next allows for users to exfiltrate potentially sensitive data of other companies.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2020-10100
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 06:07 UTC · Revision 1
Source evidence
An issue was discovered in Zammad 3.0 through 3.2. It allows for users to view ticket customer details associated with specific customers. However, the application does not properly implement access controls related to this functionality. As such, users of one company are able to access ticket data from other companies. Due to the multi-tenant nature of this application, users who can access ticket details from one organization to the next allows for users to exfiltrate potentially sensitive data of other companies.
osv:CVE-2020-10100
Complete source record
{
"id": "5d7a48460a7881299f04dd960f3045ae7f83b9dcfb56fb0bafbdc3c4030dff6b",
"url": "https://osv.dev/vulnerability/CVE-2020-10100",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2020-10100",
"summary": "An issue was discovered in Zammad 3.0 through 3.2. It allows for users to view ticket customer details associated with specific customers. However, the application does not properly implement access controls related to this functionality. As such, users of one company are able to access ticket data from other companies. Due to the multi-tenant nature of this application, users who can access ticket details from one organization to the next allows for users to exfiltrate potentially sensitive data of other companies.",
"evidence": "osv:CVE-2020-10100",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2020-10100",
"aliases": [
"CVE-2020-10100"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/zammad/zammad",
"type": "GIT",
"events": [
{
"introduced": "9bdf6d7b816d4e55501e13d12dc0d9b53cf16f5c"
},
{
"last_affected": "e0ff35cb1492d1fd09f971ead0426ea6acbbef30"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "1.0.0"
},
{
"last_affected": "3.2.0"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2020-10100.json"
}
}
],
"modified": "2026-10-24T10:30:35.639010518Z",
"provider": "osv",
"references": [
"https://zammad.com/news/security-advisory-zaa-2020-05"
],
"provider_metadata": {}
},
"related_cves": [
{
"value": "CVE-2020-10100",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 433783,
"published_at": "2020-03-05T01:15:11.303+00:00"
}