CVE-2022-23136
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 · uneditedThere is a stored XSS vulnerability in ZTE home gateway product. An attacker could modify the gateway name by inserting special characters and trigger an XSS attack when the user views the current topology of the device through the management page.
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 ZTE home gateway products. An authenticated attacker with low privileges can inject malicious JavaScript code into the gateway name field. This payload persists in the device configuration and executes when an administrator views the device topology page in the web management interface, allowing the attacker to steal session cookies or perform actions as the authenticated administrator.
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= 6.0.10p3n20CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 modelAccess the device web management interface or check device label/documentation to confirm the model is Zte Zxhn F680Affected if Device model is not Zte Zxhn F680 - this vulnerability only affects that specific model
-
Check firmware versionLog into the web management interface and navigate to the status or device information page to view the firmware version, or check via telnet/SSH if availableAffected if Firmware version is exactly 6.0.10p3n20 - this is the only version listed as affected in the advisory
-
Verify web management interface is accessibleAttempt to access the device web interface via HTTP/HTTPS on the default management IP addressAffected if Web interface is accessible and accepts authentication - the XSS payload executes when an administrator views the device topology page
-
Confirm low-privilege user access existsCheck if the device allows creation of low-privilege user accounts or if such accounts are present in the user management sectionAffected if Low-privilege user accounts can be created or exist - authentication with low privileges is required to inject the malicious script into the gateway name field
-
Inspect gateway name configurationNavigate to the device topology or network settings page where the gateway name field is displayed and check for any existing injected scripts or unexpected characters in the fieldAffected if The gateway name field contains unencoded JavaScript code or suspicious payload - this indicates the stored XSS is present
You are affected if you have a Zte Zxhn F680 device running firmware version 6.0.10p3n20 with its web management interface accessible and a low-privilege user can modify the gateway name field.
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-provided firmware patches for CVE-2022-23136; until patched, implement output encoding on all user-supplied fields displayed in the management interface and consider restricting administrative access to trusted networks.
- Consultation4.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23136 — 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-23136 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