CVE-2017-14192
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 · uneditedThe checktitle function in controllers/member/api.php in dayrui FineCms 5.0.11 has XSS related to the module field.
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 · moderate confidenceThe checktitle function in dayrui FineCms 5.0.11 (controllers/member/api.php) does not properly sanitize user-supplied input in the module field parameter, allowing injection of malicious JavaScript that executes when the unsanitized value is processed or rendered back to users.
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= 5.0.11CVSS 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 installationLocate the FineCms installation directory on the server. Common paths include /var/www/html/, /wwwroot/, or the web server document root. Look for FineCms-specific files such as index.php or configuration files.Affected if FineCms is not present on the server, the vulnerability does not apply.
-
Check FineCms versionExamine the version file or header within the FineCms installation. Typically found in a version.php, system.php, or in the admin dashboard footer. Compare the installed version to 5.0.11.Affected if The installed version is exactly 5.0.11.
-
Verify the vulnerable file existsCheck if the file controllers/member/api.php exists within the FineCms installation directory.Affected if The file controllers/member/api.php is not present, the specific vulnerable code path may not exist.
-
Confirm the checktitle functionOpen controllers/member/api.php and search for the function definition 'function checktitle' to confirm it exists in the installed version.Affected if The checktitle function is not defined in the file, the vulnerability may not be present.
-
Test the module parameter for XSSIf you have access to the member API endpoint, submit a request to the checktitle function with a test payload in the module parameter such as <script>alert(1)</script> and observe if it is reflected unescaped in the response.Affected if The module parameter value is reflected in the response without HTML encoding, confirming the XSS vulnerability is present and exploitable.
The environment is affected if FineCms version 5.0.11 is installed and the controllers/member/api.php file contains the vulnerable checktitle function with unsanitized module parameter handling.
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 the module field parameter in the checktitle function. Apply context-appropriate output encoding when the module field data is used in any HTML, JavaScript, or other reactive contexts.
- 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-14192 — 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-14192 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