Cyber Resilience

CVE-2025-56676

Titansystems Zender 3.9.7

Published
30 September 2025
Modified
18 October 2025
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
EPSS Score 0.0031 23th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2025-56676 is a medium-severity Improper Restriction of Security Token Assignment (CWE-1259) vulnerability in Titansystems Zender. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Access Token Manipulation (T1134); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-25 (Reference Monitor) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

TitanSystems Zender v3.9.7 contains an account takeover vulnerability in its password reset functionality. A temporary password or reset token issued to one user can be used to log in as another user, due to improper validation of token-user linkage. This…

more

allows remote attackers to gain unauthorized access to any user account by exploiting the password reset mechanism. The vulnerability occurs because the reset token is not correctly bound to the requesting account and is accepted for other user emails during login, enabling privilege escalation and information disclosure.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1134 Access Token Manipulation Stealth
Adversaries may modify access tokens to operate under a different user or system security context to perform actions and bypass access controls.
T1134.001 Token Impersonation/Theft Stealth
Adversaries may duplicate then impersonate another user's existing token to escalate privileges and bypass access controls.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-56207Shared CWE-1259
CVE-2025-50579Shared CWE-1259
CVE-2026-40264Shared CWE-1259
CVE-2024-29371Shared CWE-1259
CVE-2025-51306Shared CWE-1259
CVE-2024-36533Shared CWE-1259
CVE-2026-25700Shared CWE-1259
CVE-2024-36111Shared CWE-1259
CVE-2024-41948Shared CWE-1259
CVE-2024-4598Shared CWE-1259

Affected Assets

titansystems
zender
3.9.7

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

A tamperproof reference monitor ensures security tokens cannot be improperly assigned or altered outside policy.

Access enforcement directly requires that security tokens used for authorization decisions are protected from unauthorized assignment or modification.

Isolating security functions from non-security functions reduces the attack surface for tampering with token assignment logic.

Security attributes (tokens) must be associated and maintained with subjects/objects, which structurally prevents improper assignment or lack of protection.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 mostly match
prevents

Proper definition and enforcement of authorizations directly addresses improper security token restrictions.

ID.RA-09 partial match
prevents

Pre-acquisition hardware integrity checks can detect flawed token protection mechanisms before deployment.

PR.IR-01 partial match
prevents

Logical access protections can prevent exploitation of improperly assigned hardware security tokens.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Privileged access rights help ensure only authorized processes can assign or modify tokens.

finds

Security testing can detect improper token assignment but does not prevent it at design time.

prevents

Information access restriction directly limits which entities can obtain or use security tokens.

prevents

Secure architecture principles can guide token protection mechanisms but do not enforce assignment rules.

prevents

Secure coding practices reduce the likelihood of token-assignment bugs but do not define the policy.

none

Cryptography can protect token confidentiality but does not address improper assignment logic.

References