CVE-2018-6893
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.2.0 has SQL Injection: a request with s=member,c=api,m=checktitle, and the parameter 'module' with a SQL statement, lacks effective filtering.
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 confidenceSQL injection vulnerability in FineCms 5.2.0's member API (controllers/member/Api.php) in the checktitle action, where the 'module' parameter accepts unsanitized SQL statements due to lack of effective input filtering, allowing remote attackers to execute arbitrary SQL commands.
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.2.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify FineCms installationLocate FineCms by checking for common installation directories or look for FineCms-specific files (e.g., index.php, system files). Check the version file or footer for version information.Affected if The system is running FineCms version 5.2.0 exactly.
-
Confirm exact version 5.2.0Check the version declaration in the FineCms installation - typically found in a version file, configuration file, or the main index.php. Compare the installed version to the affected range.Affected if The installed version is exactly 5.2.0.
-
Locate the vulnerable API fileCheck for the presence of controllers/member/Api.php in the FineCms installation directory. This file contains the vulnerable checktitle action.Affected if The file controllers/member/Api.php exists in the FineCms installation.
-
Verify member API is accessibleAttempt to access the member API endpoint. The vulnerability is in the checktitle action. Try accessing a URL pattern like /index.php?c=member&a=api&method=checktitle or the API route configured in your FineCms installation.Affected if The member API endpoint (specifically the checktitle action) is accessible and responds to requests.
-
Check module parameter exposureInspect the checktitle action in controllers/member/Api.php. Look for the 'module' parameter handling. The vulnerability exists because this parameter accepts unsanitized SQL input.Affected if The 'module' parameter is used in SQL queries within the checktitle action without proper sanitization or parameterized queries.
The system is affected if it runs FineCms version 5.2.0 and the member API (controllers/member/Api.php) with the checktitle action is accessible, allowing the 'module' parameter to be passed unsanitized to SQL queries.
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 parameterized queries or proper input validation/sanitization for the 'module' parameter in the vulnerable API endpoint to prevent SQL injection.
- 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-2018-6893 — 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-2018-6893 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