CVE-2026-42092
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 · uneditedtitra is an open source time tracking project. In version 0.99.52, the globalsettings Meteor publication returns all global settings without any admin or role check. Any authenticated user can subscribe via DDP and receive sensitive configuration fields such as google_secret, openai_apikey, and google_clientid. At time of publication no public patch is available.
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 confidenceThe globalsettings Meteor publication in titra v0.99.52 lacks authorization checks, allowing any authenticated user to subscribe via DDP and retrieve sensitive configuration fields including google_secret, openai_apikey, and google_clientid, resulting in information disclosure of credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check titra versionLocate the installed titra version (typically in package.json, package-lock.json, or the application startup logs). Compare the version number to v0.99.52 or earlier.Affected if The installed version is v0.99.52 or earlier.
-
Identify globalsettings publicationSearch server-side code for the globalsettings Meteor publication definition (often in a /server directory). Look for Meteor.publish('globalsettings', ...).Affected if The globalsettings publication exists in the codebase.
-
Inspect publication for authorization checksExamine the globalsettings publication code. Look for this.userId checks, role validations (e.g., isAdmin, Roles.userIsInRole), or any access control logic before returning data.Affected if No authorization check (such as this.userId or role validation) is present before publishing sensitive configuration data.
-
Test DDP subscription as non-admin userConnect to the application DDP endpoint (typically port 3000) using a non-admin authenticated user account. Subscribe to the 'globalsettings' publication and inspect the returned data payload.Affected if The subscription returns sensitive fields such as google_secret, openai_apikey, or google_clientid to a non-admin user.
-
Verify exposed credential fieldsIf subscription succeeds, check whether the returned data object contains any of these keys: google_secret, openai_apikey, google_clientid.Affected if Any of these credential fields are present in the subscription response for a non-admin user.
A user is affected if running titra v0.99.52 or earlier and the globalsettings publication returns sensitive credential fields (google_secret, openai_apikey, google_clientid) to non-admin authenticated users via DDP.
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.
From vendor dataImplement role-based access control on the globalsettings publication to restrict access to admin users only; until a patch is available, consider network-level restrictions on the DDP endpoint or temporary disabling of the affected publication.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42092 — 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-2026-42092 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