CVE-2022-40603
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 cross-site scripting (XSS) vulnerability in the CGI program of Zyxel ZyWALL/USG series firmware versions 4.30 through 4.72, VPN series firmware versions 4.30 through 5.31, USG FLEX series firmware versions 4.50 through 5.31, and ATP series firmware versions 4.32 through 5.31, which could allow an attacker to trick a user into visiting a crafted URL with the XSS payload. Then, the attacker could gain access to some browser-based information if the malicious script is executed on the victim’s browser.
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 cross-site scripting (XSS) vulnerability exists in the CGI program of multiple Zyxel firewall series (ZyWALL/USG, VPN, USG FLEX, and ATP). Attackers can craft malicious URLs containing XSS payloads that, when clicked by an authenticated user, execute JavaScript in the victim's browser context, potentially exposing session data or other browser-based information.
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>= 4.32, <= 5.31>= 4.32, <= 5.31>= 4.32, <= 5.31>= 4.32, <= 5.31>= 4.32, <= 5.31>= 4.32, <= 5.31>= 4.50, <= 5.31>= 4.50, <= 5.31CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Zyxel device modelLocate the device label or access the web management interface to confirm whether the device is one of: ATP800, ATP700, ATP500, ATP200, ATP100, ATP100w, USG Flex 100w, or USG Flex 200Affected if The device is any of these models
-
Check the installed firmware versionAccess the device web interface and navigate to the System or Maintenance section to view the current firmware version, or use the CLI command to display firmware versionAffected if The firmware version cannot be determined or is not visible
-
Compare firmware against affected version rangesCompare your installed version to the vulnerable ranges: ATP series (4.32 to 5.31) or USG Flex (4.50 to 5.31)Affected if The installed firmware version falls within or overlaps the range 4.32 to 5.31 for ATP models, or 4.50 to 5.31 for USG Flex models
-
Confirm CGI program is accessibleVerify the web-based CGI interface is enabled and accessible on the deviceAffected if The CGI program interface is accessible and the device is on the network
The device is affected if it is an ATP or USG Flex model running firmware between the vulnerable version ranges and has its CGI web interface accessible.
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: ZyWALL/USG to 4.73+, VPN to 5.32+, USG FLEX to 5.32+, and ATP to 5.32+. Users should avoid clicking untrusted links to mitigate user interaction-based exploitation.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40603 — 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-2022-40603 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