CVE-2017-10970
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 · uneditedCross-site scripting (XSS) vulnerability in link.php in Cacti 1.1.12 allows remote anonymous users to inject arbitrary web script or HTML via the id parameter, related to the die_html_input_error function in lib/html_validate.php.
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 confidenceCross-site scripting (XSS) vulnerability in Cacti 1.1.12's link.php allows remote anonymous users to inject arbitrary JavaScript or HTML via the id parameter, which is then output without proper sanitization in the die_html_input_error function within lib/html_validate.php.
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= 1.1.12CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
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.
-
Confirm Cacti installation and versionLocate the Cacti installation directory and check the version.php or CHANGELOG file. Common paths include /var/www/html/cacti/ or C:\inetpub\wwwroot\cacti\. Look for a version file or check the footer of the Cacti web interface for the version number.Affected if The installed Cacti version is exactly 1.1.12
-
Verify link.php existsCheck if the file link.php exists in the Cacti web root directory (typically at /link.php or /cacti/link.php).Affected if link.php exists in the web-accessible Cacti directory and the version is 1.1.12
-
Inspect the id parameter handling in link.phpOpen link.php and examine how the id parameter is processed. Look for code that passes the id parameter without sanitization.Affected if The id parameter from user input is passed directly to output without sanitization
-
Check lib/html_validate.php for die_html_input_error functionLocate and review lib/html_validate.php in the Cacti installation. Search for the die_html_input_error function and examine whether it performs output encoding on the id parameter.Affected if The die_html_input_error function outputs the id parameter without proper HTML encoding
You are affected if Cacti version 1.1.12 is installed and the id parameter in link.php is not sanitized before being output in the die_html_input_error function.
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 to a patched version of Cacti that properly sanitizes the id parameter in link.php and implements output encoding in the die_html_input_error function.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10970 — 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-2017-10970 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