Database modification via second-order SQL injection
Published May 13, 2024 · Updated Nov 4, 2025
SQL injection in Cacti before 1.2.27 allows remote authenticated users to modify its database through crafted automation tree rules. The create_all_header_nodes() function directly concatenates an unchecked automation_tree_rule_items field into an SQL statement after the value is stored. Automation administration privileges are required to plant the value; later device or graph actions consume it, enabling database writes and paths to file reading or code execution.
Summary
What happened
SQL injection in Cacti before 1.2.27 allows remote authenticated users to modify its database through crafted automation tree rules. The create_all_header_nodes() function directly concatenates an unchecked automation_tree_rule_items field into an SQL statement after the value is stored. Automation administration privileges are required to plant the value; later device or graph actions consume it, enabling database writes and paths to file reading or code execution.
The record
- CVE
- CVE-2024-31460
- Published
- May 13, 2024
- Updated
- Nov 4, 2025
- Vendor
- The Cacti Group
- Product
- Cacti
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.2.27
- Affected versionversion=- <1.2.27
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Maintainer advisory proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo