# CVE-2025-67282: Missing authorization in n/a

> Low-privileged users can bypass authorization to access other users' data, modify workflows, and alter application settings in TIM BPM Suite.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2026
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-vhrf-h3r9-63x8

## What is CVE-2025-67282?

CVE-2025-67282 is a medium-severity missing authorization vulnerability in n/a, published on 9 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In TIM BPM Suite/ TIM FLOW through 9.1.2 multiple Authorization Bypass vulnerabilities exists which allow a low privileged user to download password hashes of other user, access work items of other user, modify restricted content in workflows, modify the applications logo and manipulate the profile of other user.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

It affects 1 product.


Products: Tim-Solutions Tim Flow.

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

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

## Is CVE-2025-67282 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-67278](https://insights.sbomify.com/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 (medium 6.5)
- [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-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-67282 and fix it if it is affected.

What it is: CVE-2025-67282 is a medium-severity missing authorization vulnerability in n/a, published on 9 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67282 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-67282/ (Markdown: https://insights.sbomify.com/CVE-2025-67282/index.md)
```

## Sources

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

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