CVE-2023-27387
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 (CSRF) in T&D Corporation and ESPEC MIC CORP. data logger products allows a remote unauthenticated attacker to conduct an arbitrary operation by having a logged-in user view a malicious page. Affected products and versions are as follows: T&D Corporation data logger products (TR-71W/72W all firmware versions, RTR-5W all firmware versions, WDR-7 all firmware versions, WDR-3 all firmware versions, and WS-2 all firmware versions), and ESPEC MIC CORP. data logger products (RT-12N/RS-12N all firmware versions, RT-22BN all firmware versions, and TEU-12N all firmware versions).
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 confidenceCross-site request forgery (CSRF) vulnerability in T&D Corporation and ESPEC MIC CORP data logger products allows a remote unauthenticated attacker to execute arbitrary operations by tricking an authenticated user into visiting a malicious webpage. The attack exploits the lack of CSRF protection in the web interface, enabling the attacker's crafted requests to be processed with the victim's authenticated session.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 device modelAccess the device web interface or check physical device label to determine if the model is one of: TR-71w, TR-72w, RTR-5w, WDR-7, WDR-3, WS-2, RT-12n, or RS-12nAffected if The device is any of these models from T&D Corporation or ESPEC MIC CORP
-
Determine firmware versionLog into the device web interface and navigate to the settings or status page to view the firmware version informationAffected if Any firmware version is installed (all versions are affected)
-
Verify web interface is accessibleAttempt to access the device IP or hostname via HTTP/HTTPS in a web browser to confirm the web interface is reachableAffected if The web interface is accessible on the network
-
Inspect web forms for CSRF protectionView the HTML source of the device web interface forms (login, settings, configuration pages) and check if forms include anti-CSRF tokens, unique session identifiers, or SameSite cookie attributesAffected if Forms lack CSRF tokens or SameSite=Strict/Lax cookie attributes
-
Check HTTP response headersUse browser developer tools or curl -I to examine HTTP response headers from the device web server for presence of CSRF-related headers or token parameters in requestsAffected if No CSRF token parameters are submitted with form requests and no protective headers are set
If you have any of the listed T&D or ESPEC MIC data logger models with their web interface accessible and the forms lack CSRF tokens or SameSite cookie protections, you are affected by this vulnerability.
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 dataSince no patched firmware versions are available, implement network segmentation to isolate data loggers from untrusted networks and consider deploying web application firewall rules to detect and block CSRF attack patterns. Users should avoid browsing untrusted sites while authenticated to these devices.
- 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-2023-27387 — 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-27387 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