CVE-2016-2313
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 · uneditedauth_login.php in Cacti before 0.8.8g allows remote authenticated users who use web authentication to bypass intended access restrictions by logging in as a user not in the cacti database.
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 confidenceThe auth_login.php script in Cacti before version 0.8.8g contains an authentication bypass vulnerability. Remote attackers who have valid web authentication credentials can exploit this flaw to log in as users that do not exist in the Cacti database, effectively bypassing intended access restrictions and potentially escalating privileges.
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<= 0.8.8f= 42.1= 13.1= 13.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Cacti versionLocate the Cacti version information - typically accessible via the Cacti web interface footer, or in a version file within the Cacti installation directory. Compare your installed version against the affected range: 0.8.8f or earlier.Affected if The installed Cacti version is 0.8.8f or any earlier version.
-
Verify auth_login.php is presentCheck if the auth_login.php script exists in the Cacti web directory. This is the script identified as containing the vulnerability.Affected if The file exists and the Cacti version is <= 0.8.8f.
-
Confirm web interface accessibilityDetermine if the Cacti web interface is exposed to network access. The vulnerability requires valid web authentication credentials to exploit, so an exposed web interface is necessary for exploitation.Affected if The Cacti web interface is externally accessible and the version is <= 0.8.8f.
-
Review user account configurationCheck the Cacti database for user records. The flaw allows attackers to log in as users that do not exist in the Cacti database, so verify expected user accounts match actual records.Affected if Unexpected user accounts appear in the system or users that should exist are missing, and version is <= 0.8.8f.
You are affected if your installed Cacti version is 0.8.8f or earlier and the web interface is accessible, because the auth_login.php script in those versions contains the authentication bypass flaw.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade Cacti to version 0.8.8g or later to obtain the patch for this vulnerability. Review user account configurations and audit access logs for any suspicious activity from the time of potential exploitation.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2313 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-2313 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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