CVE-2025-67280
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 · uneditedIn TIM BPM Suite/ TIM FLOW through 9.1.2 multiple Hibernate Query Language injection vulnerabilities exist which allow a low privileged user to extract passwords of other users and access sensitive data of another 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 confidenceMultiple Hibernate Query Language injection vulnerabilities in TIM BPM Suite/TIM FLOW through version 9.1.2 allow authenticated low-privileged users to inject malicious HQL queries via unsanitized input parameters, enabling extraction of password hashes from the user database and unauthorized access to other users' sensitive data.
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< 9.1.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Tim Flow versionLocate the Tim Flow installation and check the version from the about page, version.properties file, or admin console. Compare against the affected range.Affected if The installed version is 9.1.2 or lower
-
Confirm Hibernate ORM usageSearch the application codebase for Hibernate imports (org.hibernate.*) and usage of createQuery, createSQLQuery, or HQL string construction.Affected if The application uses Hibernate for database operations
-
Inspect HQL query constructionReview DAO and repository classes for HQL query strings. Look for patterns where user input is concatenated into query strings rather than bound as typed parameters.Affected if HQL queries are built using string concatenation with unsanitized user input
-
Verify parameter binding implementationCheck if query parameters are passed using setParameter, setString, or setInteger methods with typed binding rather than string interpolation.Affected if User-supplied parameters are inserted directly into HQL strings without parameterized binding
A user is affected if their Tim Flow version is below 9.1.3 and the application passes unsanitized user input into Hibernate queries.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.1.2
Upgrade to TIM BPM Suite/TIM FLOW version 9.1.3 or later which contains the security patches; alternatively, implement parameterized queries with Hibernate's typed parameter binding and add input validation on all user-supplied parameters used in database queries.
9.1.2
- Identify current Tim Flow/TIM BPM Suite installation version
- Plan upgrade to version 9.1.2 or later
- Backup the current installation and database before upgrading
- Upgrade Tim Flow to version 9.1.2
- Verify the upgrade was successful and the HQL injection vulnerabilities are resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67280 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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