CVE-2025-24388VulnerabilityPublished 16 Jun 2025

CVE-2025-24388: OTRS · Incomplete List of Disallowed Inputs

Affects OTRSSource CVE Database V5

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

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

3.8Low

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:H/UI:N/S:U/C:N/I:L/A:L

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

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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jun 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-26.

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

1. Restrict and monitor administrative and agent account access rigorously, implementing strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of credential compromise. 2. Conduct regular audits of user privileges and session activities to detect anomalous behavior indicative of parameter injection attempts. 3. Apply strict input validation and sanitization controls at the application layer, potentially through custom web application firewalls (WAFs) or runtime application self-protection (RASP) solutions, to detect and block suspicious parameter manipulations. 4. Isolate OTRS instances within segmented network zones with limited access to reduce lateral movement opportunities in case of compromise. 5. 6. For organizations using derived products, verify with vendors about the presence of this vulnerability and request timely remediation. 7. Implement comprehensive logging and alerting on administrative actions within OTRS to facilitate rapid incident response. 8. Consider temporary compensating controls such as disabling non-essential agent/admin interfaces or restricting access to trusted IP ranges until patches are applied.

Description

A vulnerability in the OTRS Admin Interface and Agent Interface (versions before OTRS 8) allow parameter injection due to for an autheniticated agent or admin user. This issue affects: * OTRS 7.0.X * OTRS 8.0.X * OTRS 2023.X * OTRS 2024.X * OTRS 2025.X * ((OTRS)) Community Edition: 6.0.x Products based on the ((OTRS)) Community Edition also very likely to be affected

Impact

For European organizations using OTRS, especially those relying on it for critical IT service management, customer support, or internal ticketing workflows, this vulnerability poses a risk of unauthorized parameter manipulation by authenticated agents or administrators. Although the impact on confidentiality is negligible, the integrity and availability of ticketing data and processes could be compromised, potentially leading to incorrect ticket handling, privilege escalation within the application context, or denial of service conditions. Given that OTRS is widely used in public sector institutions, healthcare, and large enterprises across Europe, exploitation could disrupt essential services and degrade operational efficiency. The requirement for authenticated high-privilege users reduces the likelihood of external attackers exploiting this vulnerability directly; however, insider threats or compromised credentials could be leveraged to exploit this flaw. The absence of known exploits in the wild suggests limited current risk, but the vulnerability should be addressed promptly to prevent future exploitation. Additionally, organizations using products derived from the ((OTRS)) Community Edition should consider themselves at risk due to probable codebase similarities.

CWE-184Incomplete List of Disallowed Inputs (opens in a new tab)
Base weaknessOWASP Top 10 A03:2021: Injection (opens in a new tab)
The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.
Implementation · Input Validation
Do not rely exclusively on detecting disallowed inputs. There are too many variants to encode a character, especially when different environments are used, so there is a high likelihood of missing some variants. Only use detection of disallowed inputs as a mechanism for detecting suspicious activity.
Attack patterns
Double Encoding (opens in a new tab)
Command Delimiters (opens in a new tab)
Flash Injection (opens in a new tab)
Using Leading 'Ghost' Character Sequences to Bypass Input Filters (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Jun 2025, 12:04 UTC

WeaknessesCWE-184

Technical details

References

Community reviews

Related threats