CVE-2019-6561
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 · uneditedCross-site request forgery has been identified in Moxa IKS and EDS, which may allow for the execution of unauthorized actions on the device.
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 confidenceCross-site request forgery (CSRF) vulnerability in Moxa IKS industrial switches and EDS Ethernet serial servers allows attackers to trick authenticated users into executing unintended administrative actions on the device via malicious web requests.
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<= 4.5<= 3.8<= 3.8<= 3.8CVSS 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.1/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 modelAccess the device web interface or check the physical device label to confirm the exact model number (IKS G6824A, EDS 405A, EDS 408A, or EDS 510A).Affected if The device is one of the four affected models listed in the CVE.
-
Check the firmware versionLog into the device web interface and navigate to the System Settings or Firmware Information page to view the installed firmware version. Compare this version against the affected ranges: <= 4.5 for IKS G6824A, <= 3.8 for EDS 405A/408A/510A.Affected if The installed firmware version is at or below the affected version threshold for your specific model.
-
Verify the web management interface is enabledConfirm that the device HTTP/HTTPS web interface is accessible and functional by attempting to reach the device login page.Affected if The web interface is enabled and the device is reachable on the network.
-
Inspect web responses for anti-CSRF protectionsLog into the device and use browser developer tools or a proxy to capture a state-changing request (such as saving settings or modifying configuration). Examine the HTTP response headers and form submissions for the presence of anti-CSRF tokens, SameSite cookie attributes, or Origin/Referer header validation.Affected if State-changing requests lack anti-CSRF tokens in form hidden fields and session cookies lack SameSite attributes, indicating the device is vulnerable.
You are affected if your device matches one of the four listed models, runs firmware at or below the specified version thresholds, has the web interface enabled, and state-changing requests lack anti-CSRF tokens or SameSite cookie protections.
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 or SameSite cookie attributes on all state-changing requests, validate Origin/Referer headers server-side, and consider implementing SameSite=Strict for session cookies.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6561 — 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-2019-6561 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