# CVE-2025-24388: Unsafe handling of AJAX calls

> Authenticated agents or admins can inject parameters via AJAX calls in OTRS, potentially escalating privileges or modifying data.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2025
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-3gw9-qxrf-m4p6

## What is CVE-2025-24388?

CVE-2025-24388 is a low-severity vulnerability in ((OTRS)) Community Edition, published on 16 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2025-24388?


## How do I fix CVE-2025-24388?

No fix has been published for CVE-2025-24388 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24388 being exploited?

There is no known exploitation of CVE-2025-24388 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24388 and fix it if it is affected.

What it is: CVE-2025-24388 is a low-severity vulnerability in ((OTRS)) Community Edition, published on 16 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24388 in the wild and no public exploit code.

Affected product: ((OTRS)) Community Edition. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24388/ (Markdown: https://insights.sbomify.com/CVE-2025-24388/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24388
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24388
- OSV: https://osv.dev/vulnerability/CVE-2025-24388

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24388/
Summaries are generated and may contain mistakes; the official description above is the record.