CVE-2018-10591
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 · uneditedIn Advantech WebAccess versions V8.2_20170817 and prior, WebAccess versions V8.3.0 and prior, WebAccess Dashboard versions V.2.0.15 and prior, WebAccess Scada Node versions prior to 8.3.1, and WebAccess/NMS 2.0.3 and prior, an origin validation error vulnerability has been identified, which may allow an attacker can create a malicious web site, steal session cookies, and access data of authenticated users.
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 an origin validation error in Advantech WebAccess (multiple versions) that allows attackers to create malicious websites to steal session cookies and access data of authenticated users. This is a cross-origin vulnerability, likely CSRF or improper CORS implementation, enabling session hijacking through malicious sites.
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<= 8.2_20170817<= 8.3.0<= 2.0.15< 8.3.1<= 2.0.3CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/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 installed Advantech WebAccess versionAccess the web interface login page or 'About' section of the application, or check version files in the installation directory if accessible. Note the exact version string.Affected if The installed version falls within these vulnerable ranges: Webaccess <= 8.2_20170817 or <= 8.3.0; Dashboard <= 2.0.15; Scada < 8.3.1; Webaccess/nms <= 2.0.3
-
Inspect CORS response headersSend an HTTP request to the application's authentication or sensitive endpoints with an arbitrary Origin header (e.g., Origin: http://malicious-site.com) and examine the response headers for Access-Control-Allow-Origin.Affected if The server returns Access-Control-Allow-Origin: * or reflects the arbitrary Origin value without validation, enabling cross-origin requests from malicious sites
-
Verify Origin header validation on sensitive requestsIntercept a legitimate authenticated request (such as a form submission or API call) and replay it with a mismatched or arbitrary Origin header to see if the server accepts it.Affected if The server accepts and processes requests with unexpected Origin headers on sensitive endpoints without rejecting them
-
Check session cookie security attributesLog in to the application and inspect the session cookie(s) in browser developer tools or via HTTP response headers. Look for the Set-Cookie header attributes.Affected if Session cookies lack the SameSite=Strict or SameSite=Lax attribute, making them vulnerable to being sent in cross-origin requests from malicious sites
-
Verify CSRF token presence on state-changing operationsReview forms that perform actions (configuration changes, user actions) and check if they include CSRF token parameters. Attempt a form submission without a token to test if it is rejected.Affected if State-changing operations (POST/PUT/DELETE requests) lack CSRF token validation and the application does not validate the Origin or Referer header
A user is affected if the installed version is within the vulnerable ranges listed AND the application lacks proper Origin header validation, uses permissive CORS settings, or serves session cookies without SameSite attributes.
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 data8.3.1
Implement proper origin validation, CSRF tokens, and SameSite cookie attributes. Additionally, configure appropriate CORS headers and validate the Origin header on sensitive requests to prevent cross-site attacks.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10591 — 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-10591 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