Skip to main content
VulnerabilityPublished

CVE-2025-67280: tim-bpm-suite · SQL Injection: Hibernate

Affects tim-bpm-suiteSource CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium : upgrade to 9.1.3 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.1.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade com.tim/tim-bpm-suite to 9.1.3.

Affected software

ProductAffectedFixed in
Mavencom.tim/tim-bpm-suitepkg:maven/com.tim/tim-bpm-suiteOther threatsAffected
  • <9.1.3
Fixed in
  • 9.1.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate mitigation should focus on restricting access to TIM BPM Suite and TIM FLOW interfaces to trusted users and networks only, minimizing exposure to untrusted actors.
  2. Implement strict input validation and parameterization of all HQL queries to prevent injection attacks; developers should review and refactor code to eliminate unsafe query constructions.
  3. Monitor application logs for unusual query patterns or access attempts indicative of injection exploitation.
  4. Enforce strong authentication and role-based access controls to limit the privileges of users, reducing the impact of any compromised account.
  5. 6. Conduct security assessments and penetration testing focused on injection vulnerabilities within BPM environments. 7. Educate users and administrators on recognizing suspicious activity and reporting incidents promptly. 8. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block HQL injection attempts as an interim protective measure.

Description

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

References

Community reviews

Loading reviews…