# CVE-2025-67278: An issue in TIM Solution GmbH TIM BPM Suite & TIM FLOW before v.9.1.2 allows a remote attacker to escalate privileges via a crafted HTTP req


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Jan 2026
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-f4rm-q33h-47w8

## What is CVE-2025-67278?

CVE-2025-67278 is a medium-severity vulnerability in n/a, published on 9 Jan 2026. 

### Official description

An issue in TIM Solution GmbH TIM BPM Suite & TIM FLOW before v.9.1.2 allows a remote attacker to escalate privileges via a crafted HTTP request

Weakness: CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Tim-Solutions Tim Flow.

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

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

## Is CVE-2025-67278 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-67280](https://insights.sbomify.com/CVE-2025-67280/): SQL injection in n/a (medium 5.4)
- [CVE-2025-67281](https://insights.sbomify.com/CVE-2025-67281/): SQL injection in n/a (medium 5.4)
- [CVE-2025-67282](https://insights.sbomify.com/CVE-2025-67282/): Missing authorization in n/a (medium 5.4)
- [CVE-2025-67279](https://insights.sbomify.com/CVE-2025-67279/): Weak cryptography in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67278 is a medium-severity vulnerability in n/a, published on 9 Jan 2026. 
Exploitation: There is no known exploitation of CVE-2025-67278 in the wild and no public exploit code.

Affected product: n/a. 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-67278/ (Markdown: https://insights.sbomify.com/CVE-2025-67278/index.md)
```

## Sources

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

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