CVE-2018-16732
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 · unedited\upload\plugins\sys\admin\Setting.php in CScms 4.1 allows CSRF via admin.php/setting/ftp_save.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in CScms 4.1's Setting.php file at the admin.php/setting/ftp_save endpoint allows attackers to trick authenticated administrators into performing unintended FTP configuration changes without proper anti-CSRF token validation.
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= 4.1CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Identify installed CScms versionLocate the version file or check the admin dashboard for the CScms version information. Typical locations include a version.php file in the application root or the admin panel's system info section.Affected if The installed version is exactly 4.1 (CScms v4.1)
-
Verify Setting.php exists in admin directoryLocate the Setting.php file in the admin directory structure, typically found at /app/Http/Controllers/Admin/ or similar admin path depending on installation.Affected if The file Setting.php exists in the admin controllers directory
-
Examine ftp_save action in Setting.phpOpen Setting.php and locate the ftp_save function/method that handles the admin.php/setting/ftp_save endpoint. Inspect the code inside this function for any CSRF token validation logic.Affected if The ftp_save function exists but contains NO token validation (no CSRF::check, no request->token, no session token verification)
-
Check FTP configuration form for CSRF tokenLocate the HTML form or view template that renders the FTP settings page in the admin interface. Examine the form for a hidden CSRF token field (often named _token, csrf_token, or similar).Affected if The FTP configuration form does NOT include a hidden CSRF token field
The environment is affected if CScms version 4.1 is installed AND the Setting.php ftp_save action lacks CSRF token validation while the FTP settings form lacks a token field.
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 anti-CSRF tokens (synchronizer token pattern) for all state-changing admin operations, specifically validating tokens in the ftp_save action within Setting.php and ensuring all admin forms include and verify CSRF tokens.
- 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-2018-16732 — 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-16732 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