CVE-2026-64880
Received Received - Intake

Blind SQL Injection in Report Filtering System

Publication date: 2026-07-21

Last updated on: 2026-07-21

Assigner: Tenable Network Security, Inc.

Description
Unsanitized user-supplied input in report filtering parameters is concatenated directly into SQL queries without proper escaping or parameterized queries, enabling blind SQL injection and unauthorized database read access.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-21
Last Modified
2026-07-21
Generated
2026-07-22
AI Q&A
2026-07-21
EPSS Evaluated
N/A
NVD
CVE-2026-64880

Affected Vendors & Products

Currently, no data is known.

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 blind SQL injection vulnerability caused by unsanitized user input in report filtering parameters. The input is directly concatenated into SQL queries without proper escaping or parameterized queries, allowing attackers to manipulate database queries and potentially read unauthorized data.

Detection Guidance

To detect SQL injection vulnerabilities like this, inspect web application logs for unusual query patterns or errors. Use tools like SQLmap to test for injection points by sending crafted input to parameters. Check for blind SQLi by monitoring database response times or error messages.

Impact Analysis

An attacker could exploit this to gain unauthorized access to sensitive data in the database, such as user credentials, personal information, or other confidential records. This could lead to data breaches, privacy violations, or further system compromise depending on the database contents.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA due to unauthorized data access. GDPR requires protection of personal data, while HIPAA mandates safeguards for protected health information. A breach could result in legal penalties, fines, and reputational damage.

Mitigation Strategies

Immediately update the application to use parameterized queries or prepared statements for all database interactions. Validate and sanitize all user-supplied input. Implement strict input validation rules and restrict database permissions to the minimum required.

Chat Assistant

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

EPSS Chart