dbcve.org
Tim FlowApplication · Tim Solutions

CVE-2025-67279

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-09
Fix available
A fix is available. Upgrade to 9.1.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
An issue in TIM Solution GmbH TIM BPM Suite & TIM FLOW before v.9.1.2 allows a remote attacker to escalate privileges via the application stores password hashes in MD5 format

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

The TIM BPM Suite and TIM FLOW applications before version 9.1.2 store password hashes using the MD5 cryptographic algorithm. MD5 is cryptographically weak and susceptible to collision attacks and rainbow table lookups, allowing remote attackers to recover plaintext passwords and escalate privileges.

MitigationUpgrade to TIM BPM Suite/TIM FLOW version 9.1.2 or later, which implements modern password hashing algorithms such as bcrypt, scrypt, or Argon2 instead of MD5.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 the Tim Flow installation directory and check the version file or about/settings panel. Common locations include the application metadata or the administration console.
    Affected if The installed version is below 9.1.2
  2. Inspect password storage configuration
    Access the Tim Flow configuration files (typically in conf/ or config/ directories) and look for authentication or security-related settings that define how passwords are stored.
    Affected if Configuration files indicate MD5 is used as the password hashing algorithm
  3. Examine stored password hash format
    If you have database or file system access, locate the user password storage (user tables or credential files) and examine the hash format. MD5 produces 32-character hexadecimal strings.
    Affected if Password hashes appear as 32-character MD5 format or the system confirms MD5 hashing is active
  4. Check authentication module settings
    Review the authentication or security module configuration to determine which cryptographic algorithm is selected for password hashing.
    Affected if The authentication module is configured to use MD5 rather than modern algorithms like bcrypt, scrypt, or Argon2

Your environment is affected if the installed Tim Flow version is below 9.1.2 and the system is configured to store password hashes using the MD5 algorithm.

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

Upgrade to TIM BPM Suite/TIM FLOW version 9.1.2 or later, which implements modern password hashing algorithms such as bcrypt, scrypt, or Argon2 instead of MD5.

Recommended fix Moderate confidence

9.1.2 or later

  1. 1. Backup the current TIM Flow database and configuration files
  2. 2. Review the TIM Flow upgrade documentation for version 9.1.2
  3. 3. Download TIM Flow version 9.1.2 or later from the official vendor source
  4. 4. Stop the TIM Flow application services
  5. 5. Execute the upgrade installer following vendor instructions
  6. 6. Verify that password hashing has been updated from MD5 to a secure algorithm (e.g., bcrypt, Argon2)
  7. 7. Restart TIM Flow services
  8. 8. Confirm all users can authenticate successfully after the upgrade
Caveat Review release notes for any configuration or workflow changes between current version and 9.1.2; test thoroughly in staging before production deployment

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

Fix this in Tim Flow Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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