dbcve.org
OtrsApplication

CVE-2025-24387

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-10
Fix available
A fix is available. Upgrade to after 2025.1.2 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in OTRS Application Server allows session hijacking due to missing attributes for sensitive cookie settings in HTTPS sessions. A request to an OTRS endpoint from a possible malicious web site, would send the authentication cookie, performing an unwanted read operation.   This issue affects: * OTRS 7.0.X * OTRS 8.0.X * OTRS 2023.X * OTRS 2024.X * OTRS 2025.x

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OTRS fails to set Secure, HttpOnly, and SameSite attributes on authentication session cookies, allowing malicious websites to trigger authenticated requests that send the session cookie to OTRS, enabling session hijacking via cross-site request attacks.

MitigationConfigure OTRS to set Secure, HttpOnly, and SameSite=Strict (or Lax) attributes on all authentication cookies to prevent cross-site transmission.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OtrsApplication
Affected:>= 7.0.0, <= 2025.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OTRS version
    Locate the OTRS version file or check via the admin interface to determine the installed version number
    Affected if The version falls within 7.0.0 to 2025.1.2 (inclusive)
  2. Inspect authentication cookie attributes
    Log into OTRS and use browser developer tools (Application/Storage tab) or a proxy to capture HTTP responses and examine the Set-Cookie headers for session cookies
    Affected if The authentication session cookies are missing the Secure flag, HttpOnly flag, or SameSite attribute
  3. Check cookie security configuration
    Review OTRS system configuration (SysConfig) for cookie-related settings, typically under Core::Cookie or similar configuration groups
    Affected if Cookie security attributes are not explicitly enabled in the configuration

Affected if running OTRS version 7.0.0 through 2025.1.2 AND authentication session cookies lack Secure, HttpOnly, or SameSite attributes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2025.1.2
Interim mitigation

Configure OTRS to set Secure, HttpOnly, and SameSite=Strict (or Lax) attributes on all authentication cookies to prevent cross-site transmission.

Fix this in Otrs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24387 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24387 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data