# CVE-2026-48211: Cross-Site Request Forgery in Import/Export Admin console


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-f36p-fv5h-jf99, UBUNTU-CVE-2026-48211

## What is CVE-2026-48211?

CVE-2026-48211 is a medium-severity vulnerability in ((OTRS)) Community Edition, published on 12 Oct 2026. 

### Official description

An authenticated administrator can be induced to delete administrative Import/Export templates through a Cross-Site Request Forgery (CSRF) attack. The OTRS AdminImportExport::TemplateDelete action does not validate the request's ChallengeToken, allowing an unauthenticated remote attacker to craft a malicious request that is executed with the privileges of an active administrator session.

This issue affects OTRS:

  *  7.0.X
  *  8.0.X
  *  2023.X
  *  2024.X
  *  2025.X
  *  2026.X before 2026.7.X

Please note that ((OTRS)) Community Edition 6.x and before are vulnerable. Products based on the ((OTRS)) Community Edition also very likely to be affected

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-48211?


## How do I fix CVE-2026-48211?

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

## Is CVE-2026-48211 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48211 and fix it if it is affected.

What it is: CVE-2026-48211 is a medium-severity vulnerability in ((OTRS)) Community Edition, published on 12 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-48211 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-2026-48211/ (Markdown: https://insights.sbomify.com/CVE-2026-48211/index.md)
```

## Sources

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

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