Skip to main content
Mallory
HighVulnerability

CVE-2026-71287: Authenticated Blind SQL Injection in Cacti sanitize_sql_column()

Published Aug 5, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS0.55%47th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-71287CWE-89 · Improper Neutralization of Special…

CVE-2026-71287 is a high-severity SQL injection vulnerability in Cacti caused by insufficient sanitization of user-controlled ORDER BY column input in sanitize_sql_column() within lib/functions.php. The function applies the regular expression allowlist preg_replace('/[^a-zA-Z0-9_().]/', '', $column) to a user-supplied column name, but this filtering still permits characters required to form SQL function expressions. As a result, payloads using constructs such as time-delay functions can pass the filter unchanged. The sanitized value is then concatenated directly into raw SQL ORDER BY clauses, creating an injection point through the sort_column GET parameter. The issue is reachable in multiple application pages, including user_log.php, utilities.php, user_domains.php, and user_group_admin.php. Successful exploitation allows an authenticated user to conduct time-based blind SQL injection against the backend database.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows any authenticated Cacti user, including low-privilege users, to execute time-based blind SQL injection against the Cacti database. This can enable extraction of sensitive database contents, inference of protected information through blind techniques, modification of stored data, and disruption of availability depending on database permissions and application context. The assigned CVSS 3.1 vector indicates potential high impact to confidentiality, integrity, and availability.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to Cacti to trusted users only and minimize the number of accounts with login capability, since exploitation requires authentication. Disable or limit exposure of affected interfaces where feasible, monitor for anomalous request patterns involving sort parameters, and apply compensating controls such as a web application firewall rule set that blocks unexpected ORDER BY expressions in sort-related parameters. Reducing database account privileges used by the application can also limit post-exploitation impact.

Remediation

Patch, then assume compromise.

Update Cacti to a vendor-patched release or the latest fixed version that corrects the unsafe handling of ORDER BY input in sanitize_sql_column() and related query construction paths. The vulnerable pattern of concatenating user-controlled values into ORDER BY clauses should be replaced with strict server-side mapping of allowed sort keys to predefined column names or expressions. After patching, review database access controls and inspect relevant application and database logs for signs of exploitation.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-71287 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-71287 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-71287?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-71287.
Is there a patch for CVE-2026-71287?
Update Cacti to a vendor-patched release or the latest fixed version that corrects the unsafe handling of ORDER BY input in sanitize_sql_column() and related query construction paths. The vulnerable pattern of concatenating user-controlled values into ORDER BY clauses should be replaced with strict server-side mapping of allowed sort keys to predefined column names or expressions.
How severe is CVE-2026-71287?
CVE-2026-71287 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.55% (47th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.