dbcve.org
CactiApplication

CVE-2026-39955

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 1.2.31 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cacti is an open source performance and fault management framework. Versions 1.2.30 and prior have pre-authentication SQL Injection via unanchored FILTER_VALIDATE_REGEXP in graph_view.php. This issue has been fixed in version 1.2.31.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cacti versions 1.2.30 and prior contain a pre-authentication SQL Injection vulnerability in graph_view.php due to an unanchored FILTER_VALIDATE_REGEXP filter. An unauthenticated attacker can inject malicious SQL statements through this filter to potentially exfiltrate, modify, or delete database contents.

MitigationUpgrade Cacti to version 1.2.31 or later. Until patched, restrict network access to Cacti instances to minimize exposure from unauthenticated attackers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CactiApplication
Affected:< 1.2.31

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Cacti version
    Locate the version file in the Cacti installation directory (e.g., 'include/cacti_version.php' or check the Cacti web interface footer), or run: grep -r 'version' include/cacti_version.php 2>/dev/null
    Affected if The installed version is 1.2.30 or any version prior to 1.2.31
  2. Verify graph_view.php exists
    Check for the presence of graph_view.php in the Cacti web root directory (typically in the 'graph_view.php' file at the web root)
    Affected if graph_view.php is present in the Cacti web directory
  3. Confirm unauthenticated access to graph_view.php
    Attempt to access graph_view.php directly via HTTP/HTTPS without providing any authentication credentials (e.g., curl http://<cacti-host>/graph_view.php)
    Affected if The page loads or responds without requiring login, indicating the pre-authentication attack surface is exposed
  4. Check FILTER_VALIDATE_REGEXP usage in graph_view.php
    Inspect the source code of graph_view.php for the FILTER_VALIDATE_REGEXP filter implementation and verify if it uses an unanchored regex pattern
    Affected if The code contains a FILTER_VALIDATE_REGEXP filter with an unanchored regex pattern that could allow SQL injection via the filter parameters

You are affected if Cacti version is 1.2.30 or prior AND graph_view.php is accessible without authentication and contains the vulnerable unanchored FILTER_VALIDATE_REGEXP filter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.31 or later
Fixed in 1.2.31
Vendor patch github.com →
Interim mitigation

Upgrade Cacti to version 1.2.31 or later. Until patched, restrict network access to Cacti instances to minimize exposure from unauthenticated attackers.

Recommended fix High confidence

Cacti 1.2.31

  1. 1. Back up your current Cacti installation and database before upgrading.
  2. 2. Download Cacti version 1.2.31 from the official Cacti website or GitHub releases.
  3. 3. Replace the existing Cacti files with the new version 1.2.31 files.
  4. 4. Run any database upgrade scripts if required (typically via the Cacti web interface).
  5. 5. Verify the upgrade was successful and test that the application functions correctly.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cacti Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39955 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39955 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data