CVE-2018-7859
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 · uneditedA security vulnerability in D-Link DGS-1510-series switches with firmware 1.20.011, 1.30.007, 1.31.B003 and older that may allow a remote attacker to inject malicious scripts in the device and execute commands via browser that is configuring the unit.
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 · moderate confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in the web management interface of D-Link DGS-1510-series switches. A remote attacker can inject malicious JavaScript code into device configuration parameters, which then executes in the browser of administrators accessing the device's web interface to configure the switch, enabling command execution through the browser session.
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.31.b003= 1.20.011= 1.30.007<= 1.31.b003= 1.20.011= 1.30.007<= 1.31.b003= 1.20.011= 1.30.007<= 1.31.b003= 1.20.011= 1.30.007<= 1.31.b003= 1.20.011= 1.30.007<= 1.31.b003= 1.20.011= 1.30.007<= 1.31.b003= 1.20.011= 1.30.007<= 1.31.b003= 1.20.011= 1.30.007CVSS 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.1/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 the switch modelAccess the device console or web interface and retrieve the hardware model information. This is typically visible on the device label, in the web interface header, or via CLI command 'show device info' or 'show system info'.Affected if The device model is any DGS-1510 series switch including DGS-1510-20, DGS-1510-28, DGS-1510-28p, DGS-1510-28x, DGS-1510-28xmp, DGS-1510-52, DGS-1510-52x, or DGS-1510-52xmp.
-
Check the firmware versionIn the web interface, navigate to the System > Firmware or System > Device Information section to view the installed firmware version. Alternatively, use CLI command 'show firmware version' or 'show version'.Affected if The installed firmware version is 1.20.011, 1.30.007, or any version up to and including 1.31.B003.
-
Verify the web management interface is enabledIn the web interface, go to Management > Web Access or similar section to confirm HTTP or HTTPS web management is enabled. In CLI, check with commands like 'show web' or 'show ip http' or 'show ip https'.Affected if The web management interface (HTTP or HTTPS) is enabled and accessible.
-
Inspect configuration parameters for injected scriptsReview all configurable fields in the web interface where user-supplied values are stored, such as device name, description fields, VLAN names, port descriptions, or management IP settings. Check the running configuration via CLI with 'show running-config' for any unexpected HTML script tags or JavaScript code within parameter values.Affected if Any configuration parameter contains raw HTML script tags, javascript: URIs, or other XSS payload patterns that were not intentionally configured by the administrator.
The device is affected if it is a DGS-1510 series switch running firmware version 1.20.011, 1.30.007, or any version up to 1.31.B003, and the web management interface is enabled.
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 dataUpgrade D-Link DGS-1510-series switches to a patched firmware version newer than 1.31.B003. If no patched firmware is available, disable the web management interface or restrict access to trusted IP addresses only.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7859 — 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-7859 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