CVE-2018-8918
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 · uneditedCross-site scripting (XSS) vulnerability in info.cgi in Synology Router Manager (SRM) before 1.1.7-6941 allows remote attackers to inject arbitrary web script or HTML via the host parameter.
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 confidenceA cross-site scripting (XSS) vulnerability exists in the info.cgi web script of Synology Router Manager (SRM) where the 'host' parameter is not properly sanitized, allowing remote attackers to inject arbitrary JavaScript or HTML that executes in the browser sessions of other users who access 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< 1.1.7-6941CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Confirm Synology Router Manager is installedAccess the router's admin interface or check system information to verify SRM is running. Look for 'Synology Router Manager' or 'SRM' in the product name/version display.Affected if The device is not running Synology Router Manager, this CVE does not apply.
-
Check the SRM version numberIn the SRM web interface, go to Control Panel > System > Information or check the version displayed on the login page or in the system status. Note the full version string (e.g., 1.1.7-6918).Affected if The installed version is lower than 1.1.7-6941 (e.g., 1.1.7-6918, 1.1.6, etc.). Compare the version numerically.
-
Verify info.cgi is accessibleAccess the SRM web interface and navigate to pages that use info.cgi, or attempt to access https://[router-ip]/cgi-bin/info.cgi?host=test directly in a browser while authenticated.Affected if The info.cgi script is accessible and responds to requests with the 'host' parameter.
-
Confirm the host parameter is not sanitizedIf you have access to the SRM file system via SSH or the File Station, locate info.cgi and examine how the 'host' parameter is handled in the code. Look for sanitization functions or lack thereof.Affected if The code does not properly sanitize or escape the 'host' parameter before reflecting it in the output.
You are affected if the device runs Synology Router Manager with a version lower than 1.1.7-6941 and the info.cgi script with the vulnerable 'host' parameter is accessible.
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 data1.1.7-6941
Upgrade Synology Router Manager to version 1.1.7-6941 or later to obtain the patched code. If immediate patching is not feasible, restrict network access to the SRM management interface to trusted users only.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8918 — 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-8918 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