dbcve.org
Web StationApplication · Synology

CVE-2018-8913

MEDIUM · 6.1 CVSS v3.0 Published 2019-04-01
Fix available
A fix is available. Upgrade to 2.1.3-0139 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Missing custom error page vulnerability in Synology Web Station before 2.1.3-0139 allows remote attackers to conduct phishing attacks via a crafted URL.

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 confidence

Synology Web Station before version 2.1.3-0139 lacks custom error pages, causing the application to display default server error responses. Attackers can craft malicious URLs that trigger these default error pages, potentially enabling phishing attacks by tricking users with deceptive or misleading error content.

MitigationUpgrade Synology Web Station to version 2.1.3-0139 or later, which includes proper custom error page handling. Alternatively, configure custom error pages at the web server level to prevent exposure of default error responses.

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
Web StationApplication
Affected:< 2.1.3-0139

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Synology Web Station is installed
    Open Synology DSM, go to Package Center, and look for Web Station in the installed package list. If you have SSH access, run 'cat /etc/packages/WebStation.json' or check via 'synopkg list --installed' to confirm presence.
    Affected if Web Station is not installed or not listed in Package Center - the CVE only affects environments with this package.
  2. Check installed Web Station version
    In DSM Package Center, click on Web Station and view the version number shown. Alternatively, via SSH run 'cat /etc/packages/WebStation.json | grep version' to retrieve the exact installed version string.
    Affected if The installed version is anything less than 2.1.3-0139 - versions before this threshold lack proper custom error page handling.
  3. Verify custom error pages are configured in Web Station
    In DSM, open Web Station > Application Settings > PHP, or check the main Web Station settings for any 'Custom Error Pages' or 'Error Page' configuration section. Confirm whether custom error page templates have been defined.
    Affected if Custom error pages are not configured or defined in Web Station settings - the vulnerability exists when default server error responses are displayed.
  4. Check web server error page configuration
    If using Web Station with Apache or Nginx, inspect the web server configuration for custom error page directives. Check /etc/httpd/conf/extra/httpd-default.conf or /etc/nginx/conf.d/ for ErrorDocument directives, and verify custom error page files exist in the configured paths.
    Affected if No custom ErrorDocument directives are found in the web server configuration, meaning the server will return default error responses.

You are affected if Synology Web Station is installed with a version lower than 2.1.3-0139 AND no custom error pages are configured at the application or web server level, causing default error responses to be displayed to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2.1.3-0139 or later
Fixed in 2.1.3-0139
Interim mitigation

Upgrade Synology Web Station to version 2.1.3-0139 or later, which includes proper custom error page handling. Alternatively, configure custom error pages at the web server level to prevent exposure of default error responses.

Fix this in Web Station Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-8913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-8913 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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