CVE-2017-11179
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 route=admin when modifying user information, and in route=register when registering a user account.
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 stored XSS vulnerabilities in the admin user modification functionality (route=admin) and user registration functionality (route=register). User-supplied input in these areas is not properly sanitized before storage and display, allowing injection of malicious JavaScript that executes in the browsers of other users who view the affected pages.
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.
-
Identify FineCMS installationCheck the web server document root for FineCMS files (common indicators: index.php with FineCMS content, /core/ directory, or check HTTP headers for FineCMS fingerprints)Affected if FineCMS is present on the server
-
Confirm admin functionality is exposedAttempt to access the admin route by navigating to the application root with '?route=admin' or the equivalent admin URL path; verify the admin interface loadsAffected if The admin user modification interface is accessible without proper authentication restrictions
-
Check registration functionality availabilityAccess the registration page via '?route=register' or the registration URL path; determine if self-registration is enabledAffected if User registration is enabled and publicly accessible
-
Inspect stored user data for unsanitized outputReview the source code of admin user listing and profile display pages for direct output of user-supplied fields (such as username, email, or custom profile fields) without HTML encoding or sanitizationAffected if User-controlled fields are rendered without proper output encoding
-
Review input sanitization in user management codeExamine the PHP files handling admin user creation/modification and registration (typically in /core/ or /application/ directories) for absence of input sanitization functions like htmlspecialchars() or strip_tags() before storing user dataAffected if No input sanitization is performed before storing user-supplied data in the database
If FineCMS is installed with accessible admin or registration functionality where user input is stored and displayed without sanitization, the environment is affected by this stored XSS vulnerability.
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 proper input validation and output encoding for all user-supplied data in the admin and registration modules. Apply context-appropriate output escaping when displaying any user-controlled data. Consider implementing a Content Security Policy (CSP) as an additional defense-in-depth measure.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11179 — 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-11179 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