dbcve.org
Wre6505 FirmwareOperating system · Zyxel

CVE-2026-7256

HIGH · 8.8 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
** UNSUPPORTED WHEN ASSIGNED ** A command injection vulnerability in the CGI program of Zyxel WRE6505 v2 firmware version V1.00(ABDV.3)C0 could allow an adjacent attacker on the LAN to execute operating system (OS) commands on a vulnerable device by sending a crafted HTTP request.

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 confidence

A command injection vulnerability exists in the CGI program of Zyxel WRE6505 v2 wireless range extender firmware V1.00(ABDV.3)C0. An adjacent attacker on the LAN can execute arbitrary operating system commands by sending a crafted HTTP request to the vulnerable CGI endpoint.

MitigationSince the device is marked UNSUPPORTED WHEN ASSIGNED with no vendor patch available, mitigate by restricting network access to the device (network segmentation/VLAN isolation), disabling unused management interfaces, and monitoring for signs of compromise.

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
Wre6505 FirmwareOperating system
Affected:= v1.00\(abdv.3\)c0

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device admin interface or check the device label to confirm it is a Zyxel WRE6505 v2 wireless range extender
    Affected if The device is a Zyxel WRE6505 v2 model
  2. Check the installed firmware version
    Log into the device web interface and navigate to the Status or Management page to view the firmware version, or check the firmware file loaded on the device
    Affected if The firmware version is exactly v1.00(ABDV.3)C0
  3. Verify the web CGI interface is accessible
    Attempt to access the device HTTP web interface on the default LAN IP address (typically 192.168.1.1 or as configured) by visiting the URL and checking if the login or status page loads
    Affected if The CGI web interface is reachable on the LAN
  4. Confirm LAN accessibility of the device
    Check if the device HTTP service is listening on the LAN interface by scanning the local network for open port 80 or 443 on the device IP address
    Affected if The device HTTP service is exposed to the LAN segment where untrusted adjacent attackers could send requests

The device is affected if it is a Zyxel WRE6505 v2 running firmware v1.00(ABDV.3)C0 and its HTTP CGI interface is accessible from the LAN segment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the device is marked UNSUPPORTED WHEN ASSIGNED with no vendor patch available, mitigate by restricting network access to the device (network segmentation/VLAN isolation), disabling unused management interfaces, and monitoring for signs of compromise.

Recommended fix High confidence
  1. Isolate the affected device on a restricted VLAN to limit the attack surface to trusted users only
  2. Implement network access control (NAC) to ensure only authorized devices can communicate with the WRE6505
  3. Monitor network traffic for suspicious HTTP requests targeting the CGI program
  4. Consider replacing the EOL WRE6505 with a currently supported range extender that receives security updates
  5. If continued use is required, disable remote management interfaces and limit local LAN access to trusted hosts only

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wre6505 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7256 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7256 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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