Is this vulnerability remotely exploitable?

Yes. Any user or service that can send requests to the affected analytics endpoints and control sort, select, or groupBy keys can potentially exploit the flaw, subject to whatever authentication the API requires.

What level of access does an attacker need?

The attacker needs sufficient privileges to reach analytics list or aggregate endpoints—typically a standard authenticated account with analytics access. They do not need database-level access; the injection occurs through the application's query builder.

What is the safest general fix pattern?

Replace direct interpolation of client-controlled identifiers with an allowlisted mapping: maintain a server-side dictionary of valid column names, map external field names to these internal identifiers, and reject any unknown or disallowed keys. Centralize this logic so all query construction paths (select, sort, groupBy, aggregate) use the same validation.

Severity:

HIGH RISK

(8.1)

SQL Injection via Unvalidated Identifiers (CWE-89) in OneUptime Analytics StatementGenerator

CVE-2026-33142

Published:

Mar 20, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Arbitrary SQL Query Manipulation in Analytics Back-End

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Arbitrary SQL Query Manipulation in Analytics Back-End

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

SQL Injection via Unvalidated Identifiers (CWE-89) in OneUptime Analytics StatementGenerator

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal