{"uuid": "aac066e0-674e-494f-b1f2-5885bd1c7f6e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-32359", "type": "seen", "source": "https://t.me/cvedetector/22198", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-32359 - Zammad Two-Factor Authentication Authentication Bypass\", \n  \"Content\": \"CVE ID : CVE-2025-32359 \nPublished : April 5, 2025, 9:15 p.m. | 1\u00a0hour, 54\u00a0minutes ago \nDescription : In Zammad 6.4.x before 6.4.2, there is client-side enforcement of server-side security. When changing their two factor authentication configuration, users need to re-authenticate with their current password first. However, this change was enforced in Zammad only on the front end level, and not when using the API directly. \nSeverity: 4.8 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-06T01:46:44.000000Z"}