# CVE-2022-40603: Cross-site scripting in ATP series firmware

> Attackers can execute malicious scripts in victims' browsers via crafted URLs, potentially stealing browser-based information from Zyxel firewall users.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-6jf5-53hp-585m

## What is CVE-2022-40603?

CVE-2022-40603 is a medium-severity cross-site scripting vulnerability in Zyxel ATP series firmware, published on 6 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-40603?

It affects 19 products.


Products: Zyxel Atp100 Firmware, Zyxel Atp100w Firmware, Zyxel Atp200 Firmware, Zyxel Atp500 Firmware, Zyxel Atp700 Firmware, Zyxel Atp800 Firmware, Zyxel Usg40 Firmware, Zyxel Usg40w Firmware, Zyxel Usg60 Firmware, Zyxel Usg60w Firmware, Zyxel Usg Flex 100w Firmware, Zyxel Usg Flex 200 Firmware, Zyxel Usg Flex 500 Firmware, Zyxel Usg Flex 50w Firmware, Zyxel Usg Flex 700 Firmware, Zyxel Vpn1000 Firmware, Zyxel Vpn100 Firmware, Zyxel Vpn300 Firmware, Zyxel Vpn50 Firmware.

## How do I fix CVE-2022-40603?

No fix has been published for CVE-2022-40603 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-40603 being exploited?

There is no known exploitation of CVE-2022-40603 in the wild and no public exploit code.

## Other vulnerabilities in Zyxel ATP series firmware

- [CVE-2023-33009](https://insights.sbomify.com/CVE-2023-33009/): Zyxel Multiple Firewalls Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2023-33010](https://insights.sbomify.com/CVE-2023-33010/): Zyxel Multiple Firewalls Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2023-28771](https://insights.sbomify.com/CVE-2023-28771/): Zyxel Multiple Firewalls OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2022-30525](https://insights.sbomify.com/CVE-2022-30525/): Zyxel Multiple Firewalls OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2020-29583](https://insights.sbomify.com/CVE-2020-29583/): Zyxel Multiple Products Use of Hard-Coded Credentials (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40603 and fix it if it is affected.

What it is: CVE-2022-40603 is a medium-severity cross-site scripting vulnerability in Zyxel ATP series firmware, published on 6 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-40603 in the wild and no public exploit code.

Affected product: Zyxel ATP series firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-40603/ (Markdown: https://insights.sbomify.com/CVE-2022-40603/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-40603
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-40603
- OSV: https://osv.dev/vulnerability/CVE-2022-40603

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-40603/
Summaries are generated and may contain mistakes; the official description above is the record.