CVE-2017-11180
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 · uneditedFineCMS through 2017-07-11 has stored XSS in the logging functionality, as demonstrated by an XSS payload in (1) the User-Agent header of an HTTP request or (2) the username entered on the login screen.
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 confidenceFineCMS through 2017-07-11 contains a stored XSS vulnerability in its logging functionality. User-supplied input from the User-Agent HTTP header and the login username field is stored in logs without proper sanitization. When administrators view these logs in the CMS backend, the malicious JavaScript payload executes.
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 dataall versionsCVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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 FineCMS installationLocate FineCMS by identifying its index.php file or characteristic directory structure (typically /application/, /skin/, /static/ folders). Check for 'FineCMS' or 'FineCMS' branding in page source or admin login page.Affected if FineCMS is present on the system
-
Verify admin log viewing accessLog into the FineCMS admin panel and navigate to the log viewing section (typically under System, Maintenance, or Logs menu). Confirm you can access the page that displays system logs.Affected if Admin user has access to view system logs in the backend
-
Examine log entries for unsanitized User-AgentView system logs in the admin interface and inspect entries for the User-Agent header. Check if raw User-Agent strings are displayed without HTML encoding (look for unescaped characters like <, >, ", ').Affected if User-Agent values appear in logs without proper HTML encoding when displayed
-
Examine log entries for unsanitized usernameView authentication or login logs. Check if usernames from failed or successful login attempts are displayed without HTML encoding.Affected if Username values appear in logs without proper HTML encoding when displayed
-
Test for stored XSS injectionSend a crafted HTTP request with a malicious User-Agent header (e.g., <script>alert(1)</script>) followed by a login attempt with a XSS payload in the username field. Then access the log viewing page as admin.Affected if The injected payload executes (triggers alert/JS) when the admin views the logs
If FineCMS is installed and the admin panel includes a log viewing feature, the system is affected because unsanitized User-Agent and username data in logs will execute JavaScript when viewed by administrators.
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 dataImplement input validation/sanitization on the username field during login and the User-Agent header before logging. Additionally, ensure all logged data is properly escaped or encoded when displayed in the admin interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11180 — 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-11180 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