CVE-2023-52718
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 connection hijacking vulnerability exists in some Huawei home routers. Successful exploitation of this vulnerability may cause DoS or information leakage.(Vulnerability ID:HWPSIRT-2023-34408) This vulnerability has been assigned a (CVE)ID:CVE-2023-52718
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 confidenceThis is a connection hijacking vulnerability affecting certain Huawei home routers. An attacker could potentially intercept or takeover existing network connections, leading to denial of service or information leakage. The high CVSS score (8.1) indicates significant impact potential.
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= 3.0.3.266= 11.0.5.19= 2.1.0.203= 3.0.3.266= 3.0.3.236= 3.0.3.242= 3.0.3.242= 3.0.3.235= 3.0.3.242CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the Huawei router modelLocate the model number on the router device label (usually on the bottom or back of the device) or log into the router admin interface and check the device information or status pageAffected if The model matches Pt9030, Ws7206, Ws7290, Ws8000, Ws8001, Ws8002, Ws8500, or Ws8502
-
Check the installed firmware versionLog into the router web admin interface (typically at 192.168.1.1 or 192.168.3.1) and navigate to the Device Information, Status, or Firmware Upgrade section to view the current firmware versionAffected if The firmware version exactly matches one of the vulnerable versions: 3.0.3.266 (Pt9030, Ws7290), 11.0.5.19 or 2.1.0.203 (Ws7206), 3.0.3.236 (Ws8000), 3.0.3.242 (Ws8001, Ws8002, Ws8502), or 3.0.3.235 (Ws8500)
-
Verify remote management is accessibleCheck if the router admin interface is accessible from the WAN/internet side, or review the router firewall or remote management settings to confirm external access is permittedAffected if Remote management or WAN access to the router admin interface is enabled, potentially allowing external attackers to exploit the connection hijacking flaw
A user is affected if they own one of the listed Huawei router models (Pt9030, Ws7206, Ws7290, Ws8000, Ws8001, Ws8002, Ws8500, Ws8502) and the installed firmware version exactly matches the vulnerable version listed for that model.
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 available firmware updates from Huawei for affected router models. If no patch is available (EOL devices), consider network segmentation or device replacement to mitigate risk.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-52718 — 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-2023-52718 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