How severe is CVE-2017-6081?

CVE-2017-6081 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2017-6081 being actively exploited?

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

What products are affected by CVE-2017-6081?

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

How do I fix CVE-2017-6081?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-6081 published?

CVE-2017-6081 was published on 2017-03-13 and last updated on 2026-06-17.

CVE-2017-6081

CVE-2017-6081 is a high-severity vulnerability in Zammad with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.8
EPSS exploit prediction: 1% (44th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-352
Affected product: Zammad
Published: 2017-03-13
Last modified: 2026-06-17

Description

A CSRF issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1. To exploit the vulnerability, an attacker can send cross-domain requests directly to the REST API for users with a valid session cookie.

Frequently asked questions

What is CVE-2017-6081?: A CSRF issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1. To exploit the vulnerability, an attacker can send cross-domain requests directly to the REST API for users with a valid session cookie.
How severe is CVE-2017-6081?: CVE-2017-6081 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-6081 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-6081?: CVE-2017-6081 primarily affects Zammad. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-6081?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-6081 published?: CVE-2017-6081 was published on 2017-03-13 and last updated on 2026-06-17.

References

Affected products (5)

cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:*
cpe:2.3:a:zammad:zammad:1.1.0:*:*:*:*:*:*:*
cpe:2.3:a:zammad:zammad:1.1.1:*:*:*:*:*:*:*
cpe:2.3:a:zammad:zammad:1.1.2:*:*:*:*:*:*:*
cpe:2.3:a:zammad:zammad:1.2.0:*:*:*:*:*:*:*

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 →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

CVE-2025-32642 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in appsbd Vite Coupon vite-coupon allows Remote Code Inclusion.This…
CVE-2025-23922 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in Harsh iSpring Embedder embed-ispring allows Upload a Web Shell to a…
CVE-2017-5145 — Critical (CVSS 10.0): An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to firmware…
CVE-2019-25729 — Critical (CVSS 9.8): PDF Signer 3.0 contains a server-side template injection vulnerability that allows unauthenticated attackers to execute…
CVE-2025-48340 — Critical (CVSS 9.8): Cross-Site Request Forgery (CSRF) vulnerability in Danny Vink User Profile Meta Manager user-profile-meta allows…
CVE-2025-2907 — Critical (CVSS 9.8): The Order Delivery Date WordPress plugin before 12.3.1 does not have authorization and CSRF checks when importing…

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →