CVE-2026-93581

OTRS does not sufficiently enforce the uniqueness of customer user identities across multiple configured CustomerUser backends. When multiple backends (e.g., database and LDAP) are configured, the uniqueness check for customer user email addresses is performed only within the selected backend, allowing an authenticated user with permission to create or modify customer users to create a customer user whose email address is already assigned to a customer user in another backend. This can result in customer-related information or email communication being associated with or exposed to the wrong customer user. This affects versions 7.0.X, 8.0.X, 2023.X, 2024.X, 2025.X, 2026.X before 2026.7.X, and OTRS Community Edition 6.x and earlier.

A CSRF vulnerability was identified in OTRS that allows an unauthenticated attacker to force an authenticated administrator's browser to execute administrative actions, such as DBUpdate log cleanup, without proper ChallengeToken validation. The attack can be performed by embedding a crafted GET request in a malicious web page. Successful exploitation can delete existing DBUpdate log entries, reducing the availability of diagnostic and historical information used for troubleshooting and auditing.

The OTRS Agent Frontend configuration endpoint can be accessed without authentication. This allows unauthenticated remote users to retrieve internal application configuration intended for use by the authenticated Agent Frontend. The exposed information may include configured frontend routes and their associated authorization groups, authentication configuration, enabled product features, third-party integration settings, and other implementation details. This affects versions 8.0.X, 2023.X, 2024.X, 2025.X, 2026.X before 2026.7.X.

A path traversal vulnerability in the OTRS SendSupportBundle functionality allows an authenticated administrator to reference file paths outside the intended directory, potentially allowing deletion of files accessible to the OTRS application process.

An OTRS administrator can enter arbitrary JavaScript into the content of an OTRS Custom Page, which is stored by the application and subsequently executed in the browser of users accessing that page. This affects OTRS versions 7.0.X, 8.0.X, 2023.X, 2024.X, 2025.X, and 2026.X before 2026.7.X.

An authenticated administrator can be induced to delete administrative Import/Export templates through a CSRF attack. The AdminImportExport::TemplateDelete action does not validate the ChallengeToken, allowing an unauthenticated remote attacker to execute a malicious request with the privileges of an active administrator session. This affects OTRS 7.0.X, 8.0.X, 2023.X, 2024.X, 2025.X, and 2026.X before 2026.7.X, as well as Community Edition 6.x and earlier.

In OTRS, previously issued authentication tokens (JWT) are not immediately invalidated when an agent or customer user account is deactivated or its password is changed. A token may remain valid until its regular expiration time, approximately 16 hours. An attacker who previously obtained a valid token can continue to access OTRS with the privileges of the affected account.

An improper input validation vulnerability in the database layer module of OTRS and ((OTRS)) Community Edition allows an unauthenticated SQL injection, which can lead to authentication bypass. This issue only affects systems where the MySQL/MariaDB server is configured with the NO_BACKSLASH_ESCAPES SQL mode.

An improper neutralization of user-controllable input in OTRS and ((OTRS)) Community Edition ticket handling allows authenticated attackers to perform reflected XSS attacks via crafted request parameters. Malicious JavaScript can be executed in the context of an authenticated agent session when the crafted link is opened.

An improper neutralization of active SVG content in OTRS or ((OTRS)) Community Edition ticket article rendering allows attackers to inject specially crafted SVG payloads via email content, leading to browser-side resource exhaustion and denial of service when affected tickets are opened by an agent or customer. The issue can be exploited without JavaScript execution and is not mitigated by the configured Content Security Policy (CSP).