CVE-2018-17366
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 · uneditedAn issue was discovered in MCMS 4.6.5. There is a CSRF vulnerability that can add an administrator account via ms/basic/manager/save.do.
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 confidenceCSRF vulnerability in MCMS 4.6.5 allows remote attackers to trick authenticated administrators into creating new admin accounts by submitting crafted requests to ms/basic/manager/save.do without proper anti-CSRF tokens.
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.6.5CVSS 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.
-
Confirm Mcms versionLocate the installed version of Mingsoft Mcms by checking the application's about page, version file, or deployment manifest. Common locations include the login page footer, a /about endpoint, or the WAR file metadata.Affected if The installed version is exactly 4.6.5
-
Identify the vulnerable endpointVerify that the endpoint ms/basic/manager/save.do exists and is accessible in the application. This is typically found in the user management or admin panel section of the web interface.Affected if The endpoint responds and accepts POST requests for user/account creation
-
Inspect save.do handler for CSRF protectionExamine the backend source code or decompiled class file handling the ms/basic/manager/save.do request. Look for CSRF token validation logic, such as checking a request parameter or session attribute for a synchronizer token.Affected if No CSRF token validation is performed before processing state-changing operations like account creation
-
Check form submissions for token presenceLog in as an administrator and inspect the HTML forms used for creating new admin/user accounts. View the page source to see if a CSRF token field is included in forms submitting to save.do.Affected if Forms submitting to save.do lack hidden CSRF token fields or have tokens that are not validated server-side
-
Test for CSRF vulnerabilityCraft a minimal HTML page with a form that auto-submits to the target save.do endpoint with parameters for a new admin account, without including any token. Open this page while authenticated to the application and observe if the account is created.Affected if The request succeeds and creates a new admin account without requiring a valid anti-CSRF token
A user is affected if running Mingsoft Mcms version 4.6.5 AND the ms/basic/manager/save.do endpoint lacks server-side CSRF token validation on account creation operations.
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) on all state-changing operations, particularly administrative functions like user management endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17366 — 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-17366 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