LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21694: Titra APIs have Improper Access Control

Titra is open source project time tracking software. Versions 0.99.49 and below have Improper Access Control, allowing users to view and edit other users' time entries in private projects they have not been granted access to. This issue is fixed in version 0.99.50.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-21694 affects Titra, an open source time tracking application. In versions 0.99.49 and earlier, authenticated users can view or edit other users’ time entries in private projects where they lack access. This creates confidentiality and integrity risk for project time data, but the available sources do not indicate public exploitation.

Executive priority

Treat as a near-term application update for teams using Titra. The business risk is unauthorized viewing or modification of private project time data. Prioritize faster if Titra contains sensitive client, billing, staffing, or project information.

Technical view

The issue is improper access control in Titra APIs, classified as CWE-284. The CVSS 3.1 score is 6.8 with network access, low privileges required, high attack complexity, no user interaction, and high confidentiality and integrity impact. The vendor advisory states the issue is fixed in version 0.99.50.

Likely exposure

Organizations running Titra versions below 0.99.50 are potentially exposed, especially if untrusted or cross-team users share the same instance. Exposure requires an authenticated user account, according to the CVSS privileges-required rating.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not listed as KEV. The risk is insider or compromised-account access to private project time entries through authorization bypass in affected API behavior.

Researcher notes

Analysis is limited to the CVE record, GitHub advisory, and linked commit. Sources identify affected versions and fix version but do not provide evidence of exploitation, broad scanning, or compensating controls beyond upgrading.

Mitigation direction

  • Upgrade Titra to version 0.99.50 or later.
  • Review vendor advisory and commit notes for deployment-specific guidance.
  • Restrict Titra access to trusted users until upgraded.
  • Audit recent time-entry changes in private projects after upgrading.

Validation and detection

  • Inventory deployed Titra versions and identify any below 0.99.50.
  • Confirm the upgraded instance reports version 0.99.50 or later.
  • Review private project permissions for unexpected users or roles.
  • Check logs for unusual time-entry access or edits by unauthorized users.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21694 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N1.65.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.8Medium
CVSS 3.1 vector shape for CVE-2026-21694Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
kromitgmbhtitra< 0.99.50Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.