CVE-2025-6265
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 · uneditedA path traversal vulnerability in the file_upload-cgi CGI program of Zyxel NWA50AX PRO firmware version 7.10(ACGE.2) and earlier could allow an authenticated attacker with administrator privileges to access specific directories and delete files, such as the configuration file, on the affected 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 path traversal vulnerability in the file_upload-cgi CGI program of Zyxel NWA50AX PRO wireless access point allows an authenticated administrator to escape the intended directory and access/delete arbitrary files, including configuration files, via specially crafted file upload requests.
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.10\(abyw.1\)<= 7.10\(acge.2\)<= 7.10\(abzl.1\)<= 7.10\(accv.1\)<= 7.10\(acgf.2\)<= 7.10\(abtg.1\)<= 7.10\(acil.2\)<= 7.10\(abtd.1\)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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 your Zyxel device modelCheck the device label or web interface system info page to confirm the exact model number (NWA50AX, NWA50AX PRO, NWA55AXE, NWA90AX, NWA90AX PRO, NWA110AX, NWA130BE, or NWA210AX)Affected if The device model is any of the eight listed models and the firmware version is at or below the version specified for that model
-
Check the installed firmware versionLog into the web administration interface and navigate to Maintenance > Firmware or System > Overview to view the current firmware version. Compare against the affected version ranges: NWA50AX <= 7.10(abyw.1), NWA50AX PRO <= 7.10(acge.2), NWA55AXE <= 7.10(abzl.1), NWA90AX <= 7.10(accv.1), NWA90AX PRO <= 7.10(acgf.2), NWA110AX <= 7.10(abtg.1), NWA130BE <= 7.10(acil.2), NWA210AX <= 7.10(abtd.1)Affected if The installed firmware version is equal to or lower than the version listed for your specific model
-
Verify the file_upload-cgi endpoint exists and is reachableIf you have CLI or web access, confirm the file_upload-cgi program is present on the device. This is typically found in the CGI-bin directory of the web interfaceAffected if The file_upload-cgi CGI program is present and accessible on the device (required for the vulnerability to be exploitable)
-
Confirm administrative web interface is exposedCheck your network configuration to determine if the administrative web interface (HTTPS port 443 or HTTP port 80) is accessible from untrusted networksAffected if The administrative interface is exposed to untrusted networks, allowing potential authenticated attackers to reach the file_upload-cgi endpoint
You are affected if your device is one of the eight listed Zyxel NWA models and your firmware version is at or below the specific version threshold for that model, with the administrative interface accessible to the attacker.
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 dataUpgrade Zyxel NWA50AX PRO firmware to version 7.10(ACGE.2) or later. If immediate patching is not possible, restrict administrative access to trusted IPs and monitor for suspicious file operation logs.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6265 — 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-6265 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