Skip to main content
CVE-2025-69288VulnerabilityPublished Updated

CVE-2025-69288: kromitgmbh titra · Improper Input Validation

Affects kromitgmbh titraSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.99.49 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Dec 2025

  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 2026-10-25.

What to do

Upgrade kromitgmbh/titra to 0.99.49.

Affected software

ProductAffectedFixed in
GitHubkromitgmbh/titrapkg:github/kromitgmbh/titraOther threatsAffected
  • <0.99.49
Fixed in
  • 0.99.49

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

AI-suggested

1. Immediately upgrade all Titra installations to version 0.99.49 or later, where the vulnerability is patched. 2. Restrict admin access strictly to trusted personnel and enforce strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of credential compromise. 3. Implement rigorous logging and monitoring of changes to the timeEntryRule field and other critical configuration parameters to detect unauthorized modifications. 4. Conduct regular audits of admin accounts and their activities to identify suspicious behavior early. 5. If upgrading is temporarily not possible, consider isolating Titra servers within segmented network zones with limited external access to reduce exposure. 6. Review and harden NodeVM execution environments, if feasible, to limit the impact of malicious code execution. 7. Educate administrators about the risks of this vulnerability and the importance of secure credential handling. 8. Employ endpoint detection and response (EDR) tools to monitor for unusual process executions or code injections related to NodeVM.

Description

Titra is open source project time tracking software. Prior to version 0.99.49, Titra allows any authenticated Admin user to modify the timeEntryRule in the database. The value is then passed to a NodeVM value to execute as code. Without sanitization, it leads to a Remote Code Execution. Version 0.99.49 fixes the issue.

References

Community reviews

Loading reviews…