CVE-2025-32359

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2025-32359
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-32359.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-32359
Published
2025-04-05T21:15:40.657Z
Modified
2026-04-10T05:25:09.404633Z
Severity
  • 8.8 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
[none]
Details

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.

References

Affected packages

Git / github.com/zammad/zammad

Affected ranges

Type
GIT
Repo
https://github.com/zammad/zammad
Events
Introduced
1f09f838a2c9e484bb4f47e1abeeca3d763d4e7d
Fixed
b775416be8964f23173fde0c64e2974ab6a1bb74
Database specific 
{
    "versions": [
        {
            "introduced": "6.4.0"
        },
        {
            "fixed": "6.4.2"
        }
    ]
}

Affected versions

6.*
6.4.0
6.4.1

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-32359.json"