dbcve.org
Tim FlowApplication · Tim Solutions

CVE-2025-67282

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-09
Fix available
A fix is available. Upgrade to 9.1.2 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
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.

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 · moderate confidence

Authorization bypass vulnerability in TIM BPM Suite/TIM FLOW through version 9.1.2 allows low-privileged users to perform unauthorized actions including downloading password hashes of other users, accessing work items belonging to other users, modifying restricted workflow content, changing the application logo, and manipulating other user profiles.

MitigationApply vendor patch or upgrade beyond version 9.1.2. Implement comprehensive authorization checks on all sensitive endpoints and enforce proper role-based access controls (RBAC) to prevent low-privileged users from accessing or modifying resources belonging to other users or administrative functions.

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
Tim FlowApplication
Affected:< 9.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 the installed TIM FLOW version
    Locate version information in the application's about page, system information panel, or version file (commonly found in config/application.properties, help/about, or admin panels). If the product is deployed as a WAR or EAR, check the manifest file or deployment descriptor.
    Affected if The installed version is lower than 9.1.2 (any version prior to and including 9.1.1, or any 9.0.x/8.x release)
  2. Confirm TIM BPM Suite/TIM FLOW product in use
    Verify that the application is indeed Tim Solutions TIM BPM Suite or TIM FLOW by checking the product name in the application header, login page, or system documentation.
    Affected if The product is TIM BPM Suite or TIM FLOW from Tim Solutions and version is below 9.1.2
  3. Test for cross-user access via API or web interface
    Using a low-privileged (non-admin) test account, attempt to access work items, user profiles, or administrative functions belonging to a different user. Check for direct URL manipulation or API endpoint access to resources outside your assigned scope.
    Affected if A low-privileged user can access, modify, or download resources belonging to other users, or access administrative functions

If TIM FLOW version is below 9.1.2, the environment is vulnerable to authorization bypass allowing low-privileged users to access unauthorized resources and functions.

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.

dbcve · scoped
Upgrade available Upgrade to 9.1.2 or later
Fixed in 9.1.2
Interim mitigation

Apply vendor patch or upgrade beyond version 9.1.2. Implement comprehensive authorization checks on all sensitive endpoints and enforce proper role-based access controls (RBAC) to prevent low-privileged users from accessing or modifying resources belonging to other users or administrative functions.

Recommended fix Moderate confidence

TIM Flow 9.1.2 or later

  1. 1. Back up the current TIM Flow installation and database
  2. 2. Consult the official TIM Flow release notes at tim-doc.atlassian.net for upgrade procedures specific to your deployment
  3. 3. Download TIM Flow version 9.1.2 or later from the official vendor distribution channel
  4. 4. Execute the upgrade following the documented migration steps
  5. 5. After upgrade, verify that the authorization controls are enforced by testing each affected function: user password hash access, cross-user work item access, workflow content modification, logo modification, and cross-user profile manipulation
  6. 6. Confirm the vulnerabilities are remediated and monitor for any abnormal behavior
Caveat Minor version upgrade within same major release; review release notes for any configuration or behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tim Flow Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,740
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67282 — 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-67282 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