High [CVE-2026-71287] Blind SQL injection due to improper input sanitization
This high-severity Red Hat Linux advisory covers CVE-2026-71287.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
Cacti's sanitize_sql_column (lib/functions.php) sanitizes user-supplied ORDER BY column names using the regex. Because this allowlist retains letters, digits, underscore, parentheses, and dot (intended to support expressions like COUNT(id) and table.column), a payload such as passes through completely unmodified.
A flaw was found in Cacti. An authenticated user, regardless of their privilege level, can exploit a vulnerability where user-supplied input for sorting database columns is not properly sanitized.
This allows for the injection of malicious SQL commands, leading to time-based blind SQL injection. The primary consequence is the potential for unauthorized access to sensitive information stored in the Cacti database.
This flaw is rated Important because any authenticated Cacti user, regardless of privilege level, can inject arbitrary SQL into the ORDER BY clause via the sort_column parameter (e.g. SLEEP(5)), since sanitize_sql_column()'s allowlist regex fails to strip parentheses.
This allows blind, time-based extraction of the entire Cacti database (C:H) and can degrade availability through sustained query delays (A:H), with no user interaction and low attack complexity required. This component is shipped only in EPEL.
Red Hat does not ship this component in any core Red Hat products.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 3 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 3 hours ago·verify at source
Mitigation checklist
- Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.
Official advisory · high-confidence parse· fetched 3 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.