Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-39955 – Pre-Auth SQL Injection – Cacti ≤ 1.2.30

Be the first to know when new zero-days emerge:

Summary

CVE-2026-39955 is a critical pre-authentication SQL injection vulnerability affecting Cacti, the open-source network performance and fault management framework, in all versions up to and including 1.2.30. The flaw arises from an unanchored FILTER_VALIDATE_REGEXP validation in graph_view.php, allowing unauthenticated remote attackers to inject arbitrary SQL commands via the rfilter parameter. A patch was released in version 1.2.31, and immediate upgrade is strongly recommended.

Technical details

  • Root cause: The rfilter parameter in graph_view.php is validated using PHP’s FILTER_VALIDATE_REGEXP, but the regular expression is unanchored — it confirms the input is a valid regex pattern but does not constrain its content, allowing SQL metacharacters to pass through and reach the underlying database query unescaped (CWE-89).
  • Trigger conditions: The vulnerable endpoint is reachable without any authentication. An attacker only needs network access to a Cacti instance to craft a malicious HTTP request targeting graph_view.php.
  • Attack vector: Remote, over the network (AV:N), with low complexity (AC:L), requiring no privileges (PR:N) and no user interaction (UI:N).
  • Impact: Full compromise of confidentiality, integrity, and availability of the Cacti database (C:H/I:H/A:H), including potential access to stored credentials and sensitive monitoring data.

Affected software

  • Cacti versions 1.2.30 and prior

Severity

CVSS v3.1 Base Score: 9.8 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to Cacti 1.2.31, which contains the fix for this vulnerability (addressed via pull requests #7039, #7054, and #7055 in the Cacti repository).
  • If immediate upgrade is not feasible, restrict network access to the Cacti web interface at the firewall or network layer to prevent unauthenticated internet-facing exposure.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge