{"uuid": "86e90da5-b879-499d-8aca-78471bbdb2a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "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"}