CVE-2025-46272
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 · uneditedWGS-80HPT-V2 and WGS-4215-8T2S are vulnerable to a command injection attack that could allow an unauthenticated attacker to execute OS commands on the host system.
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 confidenceD-Link WGS-80HPT-V2 and WGS-4215-8T2S devices contain an unauthenticated command injection vulnerability allowing remote attackers to execute arbitrary operating system commands on the affected hardware, likely through insufficient input validation in web interface parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 exact D-Link device modelLocate the physical device or check your network inventory for D-Link WGS-80HPT-V2 or WGS-4215-8T2S switches or access points. The model number is usually printed on a label on the device chassis.Affected if The device is a WGS-80HPT-V2 or WGS-4215-8T2S model
-
Check the firmware versionAccess the device web interface (if safe to do so internally) and navigate to the status or system information page to find the firmware version. Alternatively, check D-Link support pages for these models to identify the current stable release versus what you are running.Affected if The installed firmware version is older than the latest available from D-Link for these specific models
-
Determine if the web interface is externally accessibleFrom an untrusted network (such as a home ISP connection or mobile hotspot), attempt to reach the device IP address on common web ports (80, 443, 8080). Or review firewall rules to see if inbound HTTP/HTTPS to the device IP is permitted from outside your trusted network.Affected if The device web management interface is reachable from the internet or untrusted networks without VPN or firewall filtering
-
Review logs for suspicious commandsIf accessible, check the device system logs or audit logs for entries containing unusual characters often used in command injection (such as semicolons, pipes, backticks, $() syntax) or for commands you did not initiate.Affected if Logs show unexpected system commands or web requests containing shell metacharacters in parameters
-
Check for unauthorized configuration changesReview the device configuration for unexpected port forwards, firewall rule changes, new admin accounts, or modified management access settings that you did not create.Affected if Configuration contains unauthorized changes or new administrative accounts
You are affected if you operate a D-Link WGS-80HPT-V2 or WGS-4215-8T2S device with its web interface exposed to untrusted networks or if you observe command injection patterns in device logs.
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 dataRestrict external network access to these devices immediately; check D-Link for firmware updates; if no patch is available, consider network isolation or device replacement.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46272 — 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-2025-46272 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