CVE-2017-13697
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 · uneditedcontrollers/member/api.php in dayrui FineCms 5.0.11 has XSS related to the dirname variable.
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 confidenceCross-site scripting (XSS) vulnerability in dayrui FineCms 5.0.11 within controllers/member/api.php, specifically in the dirname parameter. The vulnerability allows injection of malicious scripts via unsanitized user input, potentially enabling session hijacking or credential theft against authenticated 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.
-
Check FineCms versionLocate the version identifier in your FineCms installation (commonly found in version files, footer, or system info pages). Compare it to the affected version 5.0.11.Affected if The installed version is exactly 5.0.11
-
Locate the vulnerable fileNavigate to controllers/member/api.php in your FineCms installation directory and verify the file exists.Affected if The file controllers/member/api.php exists in the installation
-
Verify dirname parameter usageOpen controllers/member/api.php and search for code that handles or processes the 'dirname' parameter from user input.Affected if The code processes a dirname parameter without visible sanitization or input validation
-
Check member module accessibilityConfirm that the member module and its API endpoints are enabled and accessible on your FineCms installation.Affected if The member module is active and the api.php endpoint is reachable without authentication restrictions
-
Inspect output handling for dirnameReview how the dirname value is output or rendered in the codebase - look for direct echo/print statements or view template usage without HTML encoding.Affected if The dirname parameter value is displayed to users without proper output encoding or escaping
Your environment is affected if you are running FineCms version 5.0.11 with the controllers/member/api.php file present and the dirname parameter being processed and displayed without sanitization.
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 dirname variable. Use context-appropriate escaping (HTML encoding for displayed content) and validate that the input conforms to expected patterns before processing or displaying.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13697 — 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-13697 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