CVE-2022-45441
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 Zyxel NBG-418N v2 firmware versions prior to V1.00(AARP.13)C0, which could allow an attacker to store malicious scripts in the Logs page of the GUI on a vulnerable device. A successful XSS attack could force an authenticated user to execute the stored malicious scripts and then result in a denial-of-service (DoS) condition when the user visits the Logs page of the GUI on the 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 · moderate confidenceA stored cross-site scripting (XSS) vulnerability exists in the Logs page of the Zyxel NBG-418N v2 router web GUI. Attackers with administrative access can inject malicious scripts that persist in the logs. When any authenticated user views the Logs page, the embedded JavaScript executes, potentially causing denial of service.
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<= 1.00\(aarp.10\)c0CVSS 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 device model and firmware versionAccess the router web GUI and check the status or firmware version page. Alternatively, check the label on the device or use the router's administration interface to locate the firmware version information.Affected if The device is a Zyxel NBG-418N v2 with firmware version 1.00(aarp.10)c0 or earlier
-
Verify the Logs page is accessibleLog into the router web GUI as an administrator and navigate to the Logs or System Logs section of the administration interface.Affected if The Logs page feature is present and accessible in the web GUI
-
Inspect existing log entries for suspicious contentView the Logs page in the router interface and examine the log entries for any unexpected or malformed data, especially entries containing HTML tags, script tags, or unusual characters that could indicate injection.Affected if Any log entries contain unescaped HTML, script tags, or JavaScript code that could execute in a browser
-
Check for unauthorized administrative accessReview any available user accounts, access logs, or session records to determine if unauthorized administrative changes may have occurred that could have introduced malicious log entries.Affected if Multiple administrative accounts exist or there are signs of unauthorized administrative access
A user is affected if they are running Zyxel NBG-418N v2 firmware version 1.00(aarp.10)c0 or earlier and can access the Logs page in the web GUI, especially if suspicious injected content appears in the logs.
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 · scopedUpgrade the firmware to version V1.00(AARP.13)C0 or later. Limit administrative access to trusted personnel and review the device regularly for any unauthorized log entries.
V1.00(AARP.13)C0
- 1. Download the fixed firmware version V1.00(AARP.13)C0 from the official Zyxel support website (www.zyxel.com) for the NBG-418N v2 device
- 2. Access the router's web-based management interface by entering the device's IP address in a web browser
- 3. Log in with administrator credentials
- 4. Navigate to the Administration or System settings section
- 5. Locate the Firmware Upgrade or Upgrade Firmware option
- 6. Click on the upgrade option and select the downloaded firmware file (V1.00(AARP.13)C0)
- 7. Initiate the firmware upgrade and wait for the upload to complete
- 8. The device will automatically reboot after the upgrade - do not power off the device during this process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45441 — 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-45441 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