Is this vulnerability remotely exploitable over the network?

Yes. Any authenticated user who can access the affected telemetry aggregation API endpoints over the network can attempt to exploit the SQL injection, without needing direct database connectivity.

Does an attacker need elevated privileges to exploit this issue?

Not necessarily. A standard authenticated user with permission to invoke telemetry aggregations is sufficient, provided they can control the aggregationType, aggregateColumnName, or aggregationTimestampColumnName parameters. Elevated privileges may increase the potential impact but are not strictly required for initial exploitation.

What is the safest general fix pattern for this vulnerability?

The most robust fix is to eliminate dynamic SQL composition from user input by using parameterized queries combined with strict allowlists. Parameters should be treated as data only, and any variable aspects of the query structure (such as allowed aggregation types or columns) must be constrained to predefined, server-controlled options.

Severity:

CRITICAL RISK

(9.9)

SQL Injection (CWE-89) in OneUptime Telemetry Aggregation API

CVE-2026-32306

Published:

Mar 13, 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 execution with potential multi-tenant data exposure, data modification, and remote code execution via database functions

Severity:

CRITICAL RISK

(9.9)

CVSS Version:

3.1

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Arbitrary SQL execution with potential multi-tenant data exposure, data modification, and remote code execution via database functions

Severity:

CRITICAL RISK

(9.9)

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 (CWE-89) in OneUptime Telemetry Aggregation API

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