Ticket information disclosure via mentions authorization bypass
Published Feb 3, 2023 · Updated Mar 26, 2025
Information disclosure in Zammad 5.3.0 allows remote authenticated users with agent permissions to view unauthorized ticket details. The /api/v1/mentions endpoint exposes ticket information across authorization boundaries, but Zammad has not published the faulty internal check. An agent account is required; the reported consequence is read-only disclosure of ticket information, with no reported modification or service interruption.
Summary
What happened
Information disclosure in Zammad 5.3.0 allows remote authenticated users with agent permissions to view unauthorized ticket details. The /api/v1/mentions endpoint exposes ticket information across authorization boundaries, but Zammad has not published the faulty internal check. An agent account is required; the reported consequence is read-only disclosure of ticket information, with no reported modification or service interruption.
The record
- CVE
- CVE-2022-48022
- Published
- Feb 3, 2023
- Updated
- Mar 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 3, 2023CVE publishedPublication date reported by the CVE source.
- Mar 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo