CVE-2017-14193
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 oauth function in controllers/member/api.php in dayrui FineCms 5.0.11 has XSS related to the Referer HTTP header with Internet Explorer.
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 oauth function in dayrui FineCms 5.0.11 (controllers/member/api.php) fails to properly sanitize the Referer HTTP header, leading to a cross-site scripting (XSS) vulnerability. This flaw is specific to Internet Explorer's handling of the Referer header, which may not encode or filter the value properly in certain contexts.
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 installed FineCms versionLocate the version file or footer/admin panel where FineCms displays its version number (commonly in system/config or admin dashboard)Affected if The installed version is 5.0.11 exactly
-
Verify oauth function exists in api.phpCheck if the file controllers/member/api.php exists and contains an oauth function/methodAffected if The file exists and contains the oauth function
-
Confirm Referer header is processed without sanitizationInspect the oauth function code in controllers/member/api.php to see if the Referer HTTP header is used directly in any output (such as redirects, logs, or response content) without proper encoding or validationAffected if The code uses $_SERVER['HTTP_REFERER'] or similar without sanitization functions like htmlspecialchars or input validation
-
Check if application is accessible via Internet ExplorerDetermine whether users access the FineCms application through Internet Explorer or IE compatibility mode, as this vulnerability is specific to IE behavior with the Referer headerAffected if Users access the site via Internet Explorer or legacy IE rendering modes
You are affected if running FineCms 5.0.11, the oauth function in controllers/member/api.php processes the Referer header without sanitization, and users access the site via Internet Explorer where the unencoded Referer value can trigger XSS.
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 Referer header in the oauth function to neutralize XSS payloads. Consider using a whitelist approach for allowed referrer domains or employing standard XSS sanitization libraries.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14193 — 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-14193 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