CVE-2023-31746
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 · uneditedThere is a command injection vulnerability in the adslr VW2100 router with firmware version M1DV1.0. An unauthenticated attacker can exploit the vulnerability to execute system commands as the root 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 · moderate confidenceThe adslr VW2100 router with firmware M1DV1.0 contains an unauthenticated command injection vulnerability that allows remote attackers to execute arbitrary system commands with root privileges. The lack of input sanitization in a web-facing parameter enables attackers to inject shell metacharacters into backend system calls.
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= m1dv1.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Confirm device model is VW2100Locate the router label or access the web administration interface to identify the model number. Look for 'VW2100' or 'Vw2100' in the device identification page or physical hardware label.Affected if The device model is identified as VW2100 from adslr manufacturer
-
Check firmware version equals M1DV1.0Access the router web interface, typically at 192.168.1.1 or 192.168.0.1, and navigate to the Status or System Information page to view the firmware version. Compare against 'M1DV1.0' or 'm1dv1.0'.Affected if Firmware version displayed is exactly M1DV1.0 (no other versions listed in the affected range)
-
Verify web management interface is enabledCheck the router web interface under Administration or Remote Management settings to confirm the HTTP/HTTPS web management service is turned on.Affected if Web-based administration interface is enabled and accessible
-
Determine if web interface is exposed to untrusted networksCheck the WAN/Internet-facing configuration in the router settings. Look for 'Remote Management', 'Web GUI Access from WAN', or similar settings that expose the interface beyond the local network.Affected if Remote management is enabled allowing access from WAN IP addresses, or the device is directly accessible from the internet on port 80/443
You are affected if you have an adslr VW2100 router running firmware version M1DV1.0 with the web management interface enabled and exposed to untrusted networks.
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 dataApply vendor firmware updates when available; if no patch exists, disable remote management interfaces, implement network segmentation to restrict access, and consider device replacement.
- 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-31746 — 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-31746 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