CVE-2024-7261
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 · uneditedThe improper neutralization of special elements in the parameter "host" in the CGI program of Zyxel NWA1123ACv3 firmware version 6.70(ABVT.4) and earlier, WAC500 firmware version 6.70(ABVS.4) and earlier, WAX655E firmware version 7.00(ACDO.1) and earlier, WBE530 firmware version 7.00(ACLE.1) and earlier, and USG LITE 60AX firmware version V2.00(ACIP.2) could allow an unauthenticated attacker to execute OS commands by sending a crafted cookie to a vulnerable device.
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 confidenceA command injection vulnerability exists in the CGI program of multiple Zyxel wireless access point and gateway devices. The 'host' parameter lacks proper input sanitization, allowing an unauthenticated attacker to inject arbitrary OS commands via a specially crafted cookie. The attack requires no authentication and can lead to full device 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< 7.00\(abtg.2\)< 6.28\(abhd.3\)< 6.70\(abvt.5\)< 7.00\(acil.2\)< 7.00\(abtd.2\)< 7.00\(acco.2\)< 7.00\(abyw.2\)< 7.00\(acge.2\)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
- 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.
-
Identify device model and firmware versionAccess the device web management interface and navigate to the Status or System Info page to view the current firmware version, or use the CLI command 'show system-info' or 'sysinfo' if available.Affected if The device is one of the listed models (NWA1123ACv3, WAC500, WAX655E, WBE530, USG LITE 60AX, or any NWA variant) and the firmware version falls below the specified version for that model.
-
Verify web CGI interface accessibilityConfirm the device's web management interface (HTTP/HTTPS on port 80/443 or alternate management ports) is reachable. This vulnerability exploits the CGI program that handles the 'host' parameter.Affected if The web interface is exposed to untrusted networks, as the vulnerability can be exploited by sending crafted cookies to the CGI endpoint without authentication.
-
Check for unauthorized command execution indicatorsReview device logs for suspicious entries, particularly in /var/log/messages or through the web interface logs section. Look for unexpected or unfamiliar commands, especially those involving shell execution or system manipulation.Affected if Logs contain commands or system calls that were not initiated by legitimate administrators, or show unexpected CGI program invocations with unusual parameter values.
-
Compare installed version against affected rangesMatch your device's exact firmware version string (for example, 6.70abvt.5 or 7.00abtd.2) against the listed vulnerable versions. For NWA models: versions below 7.00(abtg.2), 6.28(abhd.3), 6.70(abvt.5), 7.00(acil.2), 7.00(abtd.2), 7.00(acco.2), 7.00(abyw.2), or 7.00(acge.2) are affected.Affected if The installed firmware version number is lower than any of the patched versions listed for your specific model.
The device is affected if it is a Zyxel NWA access point or USG LITE 60AX running a firmware version lower than the patched releases listed, with the web management interface accessible to potential attackers.
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 · scoped6.286.707.00
Apply vendor-supplied firmware updates immediately; until patches are available, consider restricting network access to affected devices' management interfaces or placing them behind a firewall.
Model-specific firmware: Nwa110ax to 7.00(abtg.2), Nwa1123 Ac Pro to 6.28(abhd.3), Nwa1123acv3 to 6.70(abvt.5), Nwa130be to 7.00(acil.2), Nwa210ax to 7.00(abtd.2), Nwa220ax 6e to 7.00(acco.2), Nwa50ax to 7.00(abyw.2), Nwa50ax Pro to 7.00(acge.2)
- 1. Identify the specific NWA model from the list: Nwa110ax, Nwa1123 Ac Pro, Nwa1123acv3, Nwa130be, Nwa210ax, Nwa220ax 6e, Nwa50ax, or Nwa50ax Pro
- 2. Access the Zyxel support website at www.zyxel.com and navigate to the firmware download section for your specific model
- 3. Download the firmware version equal to or newer than the fixed version for your model: Nwa110ax: 7.00(abtg.2), Nwa1123 Ac Pro: 6.28(abhd.3), Nwa1123acv3: 6.70(abvt.5), Nwa130be: 7.00(acil.2), Nwa210ax: 7.00(abtd.2), Nwa220ax 6e: 7.00(acco.2), Nwa50ax: 7.00(abyw.2), Nwa50ax Pro: 7.00(acge.2)
- 4. Access the device web management interface or CLI
- 5. Upload and apply the firmware update following Zyxel's standard firmware upgrade procedure
- 6. After reboot, verify the firmware version matches the fixed release
- 7. Confirm the CGI program has been patched by checking Zyxel release notes or contacting Zyxel support
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7261 — 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-2024-7261 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