CVE-2018-18991
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 · uneditedReflected cross-site scripting (non-persistent) in SCADA WebServer (Versions prior to 2.03.0001) could allow an attacker to send a crafted URL that contains JavaScript, which can be reflected off the web application to the victim's browser.
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 confidenceThis is a reflected (non-persistent) cross-site scripting vulnerability in the SCADA WebServer application. An attacker can craft a malicious URL containing JavaScript code that gets reflected back to the victim's browser when they visit the link, allowing session hijacking or credential theft.
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< 2.03.0001CVSS 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 if Spidercontrol SCADA WebServer is runningCheck running services or processes on the system for Spidercontrol SCADA WebServer, or attempt to access the web interface on common ports (typically port 80/443 or configured HTTP port)Affected if The Spidercontrol SCADA WebServer service is found running and accessible via HTTP/HTTPS
-
Determine the installed versionCheck the application version through the web interface (often displayed in a status or about page), check installed software listings, or query the application directly via its API or banner grabbingAffected if The version cannot be determined or is displayed as a version lower than 2.03.0001
-
Compare version against affected rangeCompare your identified version number to the affected range: versions less than 2.03.0001 are vulnerableAffected if The installed version is below 2.03.0001 (for example, 2.02.x, 2.01.x, 1.x, etc.)
-
Verify web interface is accessibleConfirm the SCADA WebServer HTTP interface is reachable and functional by accessing it via browser or curl/wget commandAffected if The web interface is exposed and accepts user input through URL parameters
You are affected if Spidercontrol SCADA WebServer is running with a version lower than 2.03.0001 and its web interface is accessible, as the reflected XSS vulnerability exists in URL parameter handling.
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 data2.03.0001
Upgrade the SCADA WebServer to version 2.03.0001 or later. Additionally, implement proper input validation and output encoding on all user-controllable input fields to prevent XSS.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18991 — 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-18991 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