{"vulnerability": "CVE-2025-32359", "sightings": [{"uuid": "fe569373-a08f-477f-9f61-d8f4c6433cde", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-32359", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lm4aykf7sx2q", "content": "", "creation_timestamp": "2025-04-06T01:07:12.809446Z"}, {"uuid": "86e90da5-b879-499d-8aca-78471bbdb2a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-32359", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/10612", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-32359\n\ud83d\udd25 CVSS Score: 4.8 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)\n\ud83d\udd39 Description: 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.\n\ud83d\udccf Published: 2025-04-05T00:00:00.000Z\n\ud83d\udccf Modified: 2025-04-05T21:00:40.126Z\n\ud83d\udd17 References:\n1. https://zammad.com/en/advisories/zaa-2025-02", "creation_timestamp": "2025-04-05T21:37:52.000000Z"}, {"uuid": "aac066e0-674e-494f-b1f2-5885bd1c7f6e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "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"}]}