How severe is CVE-2023-50453?

CVE-2023-50453 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2023-50453 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (39th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2023-50453?

CVE-2023-50453 primarily affects Zammad. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2023-50453?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2023-50453 published?

CVE-2023-50453 was published on 2023-12-10 and last updated on 2026-06-17.

CVE-2023-50453

CVE-2023-50453 is a medium-severity vulnerability in Zammad with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
EPSS exploit prediction: 0% (39th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Zammad
Published: 2023-12-10
Last modified: 2026-06-17

Description

An issue was discovered in Zammad before 6.2.0. It uses the public endpoint /api/v1/signshow for its login screen. This endpoint returns internal configuration data of user object attributes, such as selectable values, which should not be visible to the public.

Frequently asked questions

What is CVE-2023-50453?: An issue was discovered in Zammad before 6.2.0. It uses the public endpoint /api/v1/signshow for its login screen. This endpoint returns internal configuration data of user object attributes, such as selectable values, which should not be visible to the public.
How severe is CVE-2023-50453?: CVE-2023-50453 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2023-50453 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (39th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-50453?: CVE-2023-50453 primarily affects Zammad. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2023-50453?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2023-50453 published?: CVE-2023-50453 was published on 2023-12-10 and last updated on 2026-06-17.

References

https://zammad.com/en/advisories/zaa-2023-08

Affected products (3)

cpe:2.3:a:zammad:zammad:6.1.0:-:*:*:*:*:*:*
cpe:2.3:a:zammad:zammad:6.1.0:alpha:*:*:*:*:*:*
cpe:2.3:a:zammad:zammad:6.2.0:alpha:*:*:*:*:*:*

More vulnerabilities in Zammad

CVE-2022-48021 — Critical (CVSS 9.8): A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary code or escalate privileges via a crafted…
CVE-2022-35490 — Critical (CVSS 9.8): Zammad 5.2.0 is vulnerable to privilege escalation. Zammad has a prevention against brute-force attacks trying to guess…
CVE-2021-42090 — Critical (CVSS 9.8): An issue was discovered in Zammad before 4.1.1. The Form functionality allows remote code execution because…
CVE-2021-42094 — Critical (CVSS 9.8): An issue was discovered in Zammad before 4.1.1. Command Injection can occur via custom Packages.
CVE-2020-26030 — Critical (CVSS 9.8): An issue was discovered in Zammad before 3.4.1. There is an authentication bypass in the SSO endpoint via a crafted…
CVE-2017-6080 — Critical (CVSS 9.8): An issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1, caused by lack of a…

All CVEs affecting Zammad →