CVE-2026-72565
Received Received - Intake

SQL Injection in APIJSON via @having Operator

Publication date: 2026-08-10

Last updated on: 2026-08-10

Assigner: 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c

Description
A SQL injection vulnerability in Tencent APIJSON through 8.1.8 allows unauthenticated remote attackers to bypass per-table access control and read arbitrary database tables via the Map-form @having operator.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-10
Last Modified
2026-08-10
Generated
2026-08-10
AI Q&A
2026-08-10
EPSS Evaluated
N/A
NVD
CVE-2026-72565
EUVD
EUVD-2026-55241

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
tencent apijson 8.1.8

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a SQL injection vulnerability in Tencent APIJSON through version 8.1.8. It allows unauthenticated remote attackers to bypass per-table access control and read arbitrary database tables using the Map-form @having operator. The issue occurs because the APIJSONORM library's AbstractSQLConfig.java only checks the per-role allow-list on the String form of @having, not the Map form, enabling attackers to inject raw SQL fragments.

Detection Guidance

To detect this SQL injection vulnerability in APIJSON, inspect HTTP requests for the @having parameter in Map form. Look for raw SQL fragments or unexpected table access patterns in logs. Check for unauthenticated requests bypassing access controls.

Impact Analysis

An attacker could exploit this to read sensitive data from database tables that should be restricted, even those configured with empty access lists. This could lead to unauthorized data exposure, data breaches, or further attacks like data manipulation or deletion if combined with other vulnerabilities.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR (data protection), HIPAA (health data), or other regulations by enabling unauthorized access to sensitive data. Organizations using APIJSON may face legal penalties, reputational damage, and loss of trust due to data breaches.

Mitigation Strategies

Upgrade APIJSON to a patched version beyond 8.1.8. Apply strict input validation for @having parameters. Disable Map-form @having usage if not required. Implement WAF rules to block suspicious SQL injection patterns in API requests.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72565. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart