CVE-2023-5961
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 · uneditedA Cross-Site Request Forgery (CSRF) vulnerability has been identified in ioLogik E1200 Series firmware versions v3.3 and prior. An attacker can exploit this vulnerability to trick a client into making an unintentional request to the web server, which will be treated as an authentic request. This vulnerability may lead an attacker to perform operations on behalf of the victimized user.
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 confidenceCSRF vulnerability in the web interface of ioLogik E1200 Series industrial controllers (firmware v3.3 and prior). Attackers can craft malicious requests that execute when an authenticated user visits a crafted page or clicks a malicious link, allowing unauthorized operations on the device.
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< 3.3< 3.3< 3.3< 3.3< 3.3< 3.3< 3.3< 3.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
- 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 ioLogik E1200 model numberLocate the device label on the physical unit or access the web interface login page to view the model identificationAffected if The model is one of E1210, E1211, E1212, E1213, E1214, E1240, E1241, or E1242
-
Check the installed firmware versionAccess the device web interface and navigate to System Settings or System Information page to view the firmware version. Alternatively, check via CLI or device documentation.Affected if The firmware version displayed is less than 3.3 (for example, 3.2, 3.1, 3.0, or earlier)
-
Verify the web interface is accessibleAttempt to reach the device web interface via HTTP/HTTPS on the configured IP address. Confirm the login page loads.Affected if The web interface is reachable on the network and the device is operational
-
Confirm no anti-CSRF protections are presentInspect the HTML forms in the web interface source code. Check if forms include anti-CSRF tokens or if SameSite cookie attributes are set.Affected if Forms lack CSRF tokens and cookies lack SameSite attributes, indicating the vulnerability is exploitable
A user is affected if they have an ioLogik E1200 Series device (E1210-E1242) running firmware version 3.3 or lower with the web interface enabled.
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.
dbcve · scoped3.3
Update firmware to latest version if available, or implement anti-CSRF tokens and SameSite cookie attributes in the web application to validate request authenticity.
Moxa ioLogik E1200 Series firmware v3.4 or later (confirm the specific fixed release version from Moxa's firmware release notes)
- 1. Identify the current firmware version of the affected ioLogik E1200 Series device (E1210, E1211, E1212, E1213, E1214, E1240, E1241, or E1242) via the web interface or administrative console
- 2. Download the latest firmware version from the official Moxa support website (www.moxa.com) - locate the ioLogik E1200 Series firmware download page
- 3. Review the firmware release notes to confirm the version includes the CVE-2023-5961 CSRF vulnerability fix
- 4. Back up the current device configuration before proceeding with firmware upgrade
- 5. Access the device's firmware upgrade function through the web interface or administrative tool
- 6. Upload and install the updated firmware file
- 7. After reboot, verify the new firmware version is installed and confirm the device is functioning normally
- 8. Test that CSRF protections are functioning by verifying anti-CSRF tokens are required for state-changing operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5961 — 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-2023-5961 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