CVE-2018-13993
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 · uneditedThe WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions 1.0 to 1.34 is prone to CSRF.
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 confidenceThe WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, and 48xx network switches (versions 1.0 to 1.34) lacks proper Cross-Site Request Forgery (CSRF) protection. An authenticated user can be tricked into unknowingly submitting unintended requests to the WebUI via malicious links or pages, potentially allowing attackers to perform unauthorized configuration changes.
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.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 device model and firmware versionLog into the WebUI of the FL SWITCH device and navigate to System > System Info or Help > About. Record the exact firmware version displayed.Affected if The displayed firmware version is between 1.0 and 1.34 inclusive.
-
Confirm the device model is in the affected product listVerify that the device model is one of: FL SWITCH 3005, 3005t, 3004t Fx, 3004t Fx St, 3008, 3008t, 3006t 2fx, or 3006t 2fx St.Affected if The device model matches one of these listed models.
-
Verify WebUI is accessibleAttempt to access the device WebUI over HTTP/HTTPS by entering the device IP address in a web browser.Affected if The WebUI login page loads and authentication is possible.
-
Check for anti-CSRF tokens in state-changing requestsUse browser developer tools or a proxy to capture HTTP requests when performing configuration changes (e.g., saving settings, modifying network parameters). Inspect each POST request for a unique token parameter that validates the request origin.Affected if State-changing POST requests lack anti-CSRF token parameters and do not validate Origin or Referer headers.
If the device is an affected FL SWITCH model running firmware version 1.0 to 1.34 and its WebUI is accessible without anti-CSRF token protection, the environment is affected by CVE-2018-13993.
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 dataImplement anti-CSRF tokens for all state-changing operations in the WebUI, and validate Origin/Referer headers. If vendor firmware update is available, apply it. Consider network segmentation to limit exposure of the WebUI to trusted users only.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13993 — 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-13993 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