CVE-2025-24391VulnerabilityPublished 14 Jul 2025

CVE-2025-24391: OTRS · Observable Discrepancy

Affects OTRSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 2026.0.0 : update OTRS when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2026.0.0, 2025.0.0, 2024.0.0 +2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
OTRS AG OTRS	Affected >=7.0.0 <7.1.0 >=8.0.0 <8.1.0 >=2023.0.0 <2024.0.0 >=2024.0.0 <2025.0.0 >=2025.0.0 <2026.0.0	Fixed in 7.1.0 8.1.0 2024.0.0 2025.0.0 2026.0.0

AI-suggested

2) If patches are not yet available, configure the external interface to standardize HTTP response codes and messages for both valid and invalid user queries, thereby eliminating observable differences that enable enumeration. 3) Implement rate limiting and anomaly detection on the external interface to detect and block automated enumeration attempts. 4) Employ web application firewalls (WAFs) with custom rules to identify and mitigate suspicious probing behavior targeting user enumeration. 5) Educate users and administrators about the risks of phishing and social engineering, emphasizing vigilance against suspicious emails that may result from leaked user information. 6) Regularly audit logs for unusual access patterns or repeated failed attempts to enumerate users. These steps go beyond generic advice by focusing on response standardization, proactive detection, and user awareness tailored to this specific vulnerability.

Description

A vulnerability in the External Interface of OTRS allows conclusions to be drawn about the existence of user accounts through different HTTP response codes and messages. This enables an attacker to systematically identify valid email addresses. This issue affects: * OTRS 7.0.X * OTRS 8.0.X * OTRS 2023.X * OTRS 2024.X * OTRS 2025.X

Impact

For European organizations using OTRS versions affected by this vulnerability, the primary impact is the exposure of valid user email addresses through user enumeration. This can facilitate targeted phishing campaigns, spear-phishing, and social engineering attacks, increasing the risk of credential compromise or unauthorized access. While the vulnerability does not directly allow system compromise or data manipulation, the leakage of user existence information undermines privacy and can be a stepping stone for more severe attacks. Organizations in sectors with sensitive customer or employee data, such as finance, healthcare, and government, are particularly at risk. The medium severity rating suggests that while the vulnerability is not critical, it still poses a meaningful threat to confidentiality and should be addressed promptly to reduce the attack surface and protect user information.

CWE-203Observable Discrepancy (opens in a new tab)
Base weakness
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Black Box Reverse Engineering (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

otrs.com/release-notes/otrs-security-advisory-2025-07/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2025, 08:46 UTC

WeaknessesCWE-203

Technical details

References

Community reviews

Related threats