CVE-2018-16730
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\Install.php in CScms 4.1 has XSS via the site name.
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 confidenceCScms 4.1 contains a stored cross-site scripting (XSS) vulnerability in the Install.php plugin file. The site name parameter does not properly sanitize user-supplied input, allowing an attacker to inject malicious JavaScript code that executes when other users view the affected page.
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
- 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 CScms installation and versionLocate the CScms installation directory and check the version number in the system configuration files or about page. Common locations include the admin panel or a version.php file.Affected if The installed version is exactly 4.1 of Chshcms Cscms
-
Locate the Install.php plugin fileNavigate to the plugins or application directory and find Install.php. This file is typically in the plugins folder of the CScms installation.Affected if The Install.php file exists in the CScms installation and contains a site name parameter input field
-
Check site name parameter handling in Install.phpOpen Install.php and examine how the site name parameter is processed. Look for the code that handles the site name input and check if it performs any input sanitization or validation.Affected if The site name parameter in Install.php lacks proper input validation (no HTML encoding, no sanitization functions)
-
Verify output encoding for site nameCheck if the application uses output encoding functions (such as htmlspecialchars) when displaying the site name value in the browser. Review the code that renders the site name on pages.Affected if The site name is displayed without HTML encoding or other output escaping mechanisms
-
Check for stored XSS in databaseIf possible, examine the database table where site configuration is stored. Look for any stored malicious JavaScript payloads in the site name field.Affected if The site name field in the database contains unsanitized script tags or JavaScript event handlers
You are affected if you are running CScms version 4.1 and the Install.php plugin processes the site name parameter without proper input validation and output encoding.
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 site name parameter in Install.php. All user-supplied data should be sanitized before storage and HTML-escaped before rendering to prevent script execution.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16730 — 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-16730 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