dbcve.org
CactiApplication

CVE-2026-39893

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. In versions 1.2.30 and prior, the rfilter request variable was concatenated into a RLIKE SQL clause without sanitization. The endpoint does not require authentication (graph viewing supports guest access via the configured guest user), so the SQLi was reachable pre-auth on installs with guest viewing enabled. This issue was 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 SQL injection vulnerability in the graph viewing functionality. The 'rfilter' request parameter is concatenated directly into a SQL RLIKE clause without sanitization, allowing attackers to inject arbitrary SQL queries.

MitigationUpgrade Cacti to version 1.2.31 or later. Additionally, if guest viewing is not required, disable the guest user configuration to eliminate the pre-authentication attack vector.

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. Identify the installed Cacti version
    Access the Cacti admin console and navigate to Configuration > Settings > General, or check the version displayed on the login page. Alternatively, inspect the include/version.php file in the Cacti installation directory.
    Affected if The installed version is 1.2.30 or any version prior to 1.2.31
  2. Verify if graph viewing is accessible to unauthenticated users
    Check the guest user configuration under Configuration > Users > Guest. Confirm whether the guest account is enabled and has permissions to view graphs.
    Affected if The guest user is enabled and granted graph view permissions, allowing unauthenticated access to the vulnerable parameter
  3. Confirm whether the rfilter parameter is processed in graph views
    Inspect the HTTP requests when accessing graph pages. The rfilter parameter is used in graph viewing functionality - try accessing a graph view URL and observe if rfilter is accepted as a request parameter.
    Affected if The rfilter parameter can be submitted to graph viewing pages without sanitization, which occurs when graph viewing is enabled

You are affected if your Cacti installation is version 1.2.30 or earlier AND graph viewing functionality is accessible (either through an enabled guest account or authenticated user sessions).

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. Additionally, if guest viewing is not required, disable the guest user configuration to eliminate the pre-authentication attack vector.

Recommended fix High confidence

1.2.31

  1. Upgrade Cacti to version 1.2.31 or later by downloading the latest release from the official Cacti repository or website
  2. After upgrading, verify the installation is working correctly by accessing the web interface
  3. If using guest user access for graph viewing, ensure it is properly configured according to your security policy - consider disabling guest access if not required
  4. Review the application logs to confirm the upgrade was successful and no errors are present
Caveat Point release upgrade (1.2.30 to 1.2.31) with no expected breaking changes; standard backup recommended before any upgrade

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

Fix this in Cacti Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39893 — 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-39893 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