dbcve.org
OneuptimeApplication · Hackerbay

CVE-2026-33142

HIGH · 8.1 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 10.0.34 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
OneUptime is a solution for monitoring and managing online services. Prior to version 10.0.34, the fix for CVE-2026-32306 (ClickHouse SQL injection via aggregate query parameters) added column name validation to the _aggregateBy method but did not apply the same validation to three other query construction paths in StatementGenerator. The toSortStatement, toSelectStatement, and toGroupByStatement methods accept user-controlled object keys from API request bodies and interpolate them as ClickHouse Identifier parameters without verifying they correspond to actual model columns. ClickHouse Identifier parameters are substituted directly into queries without escaping, so an attacker who can reach any analytics list or aggregate endpoint can inject arbitrary SQL through crafted sort, select, or groupBy keys. This issue has been patched in version 10.0.34.

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 confidence

OneUptime analytics endpoints suffer from SQL injection via three unauthenticated query construction methods (toSortStatement, toSelectStatement, toGroupByStatement) in StatementGenerator. These methods accept user-controlled keys from API request bodies and pass them as ClickHouse Identifier parameters without validation, allowing arbitrary SQL injection when an attacker crafts malicious sort, select, or groupBy keys.

MitigationUpgrade to OneUptime version 10.0.34 or later, which applies column name validation to all query construction paths. Until patched, restrict access to analytics endpoints via network controls or authentication.

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
OneuptimeApplication
Affected:< 10.0.34

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm OneUptime installation
    Locate the OneUptime installation and identify the version number in the package.json, version file, or installation manifest. For containerized deployments, check the image tag or docker-compose.yml version.
    Affected if The installed version is Hackerbay Oneuptime prior to version 10.0.34
  2. Identify analytics endpoint exposure
    Review your API gateway, reverse proxy, or firewall rules to determine if analytics-related endpoints are publicly accessible or accessible without authentication. Look for routes containing /analytics, /analytics/summary, or similar paths.
    Affected if Analytics endpoints are exposed to unauthenticated or untrusted network access
  3. Check for ClickHouse usage
    Verify that ClickHouse is configured as the database backend for OneUptime analytics by examining the configuration files, environment variables (CLICKHOUSE_HOST, CLICKHOUSE_URL), or database connection settings.
    Affected if ClickHouse is used as the analytics database backend
  4. Inspect API request handling for analytics
    Examine the StatementGenerator module or its equivalent in your installation to see if the toSortStatement, toSelectStatement, or toGroupByStatement methods process request parameters without column name validation. Review the code path from API request handlers to these methods.
    Affected if The vulnerable StatementGenerator methods accept user input directly without validating that keys match known safe column names

You are affected if you are running any version of Hackerbay Oneuptime prior to 10.0.34 with ClickHouse-backed analytics endpoints accessible to unauthenticated or untrusted users, where the StatementGenerator methods process user-controlled keys without column validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.34 or later
Fixed in 10.0.34
Interim mitigation

Upgrade to OneUptime version 10.0.34 or later, which applies column name validation to all query construction paths. Until patched, restrict access to analytics endpoints via network controls or authentication.

Recommended fix High confidence

10.0.34

  1. Upgrade OneUptime to version 10.0.34 or later to address the SQL injection vulnerability in StatementGenerator methods (toSortStatement, toSelectStatement, toGroupByStatement)
  2. After upgrading, verify that analytics list and aggregate endpoints properly validate column names in sort, select, and groupBy parameters

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Oneuptime Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33142 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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