CVE-2022-48255
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 system command injection vulnerability in BiSheng-WNM FW 3.0.0.325. A Huawei printer has a system command injection vulnerability. Successful exploitation could lead to remote code execution.
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 system command injection vulnerability exists in BiSheng-WNM FW version 3.0.0.325, a firmware used in certain Huawei printers. The vulnerability allows unauthenticated attackers to inject and execute arbitrary system commands on the affected device, potentially leading to complete device compromise and network pivoting.
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.0.325CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 device firmware versionAccess the printer's web management interface or check the device configuration/settings menu for firmware version information. Alternatively, use SNMP or the printer's diagnostic page to retrieve the firmware build number.Affected if The displayed firmware version is exactly 3.0.0.325
-
Confirm BiSheng-WNM firmware is in useVerify through the printer's status page or administrative interface that the firmware is identified as BiSheng-WNM or Huawei Bisheng WNM.Affected if The firmware is identified as BiSheng-WNM version 3.0.0.325
-
Verify network service exposureScan the device's IP address for open HTTP/HTTPS ports (typically 80, 443, 8080) used by the web management interface. Use tools like nmap or curl to confirm the web service is reachable.Affected if The printer's web management interface is accessible over the network (no firewall or ACL blocking)
-
Check for unauthenticated access to web endpointsAttempt to access the printer's web interface without credentials. Try common paths like /, /main.html, or /status.html to see if unauthenticated access is possible.Affected if The web management interface allows unauthenticated access to command injection entry points
The device is affected if it is a Huawei printer running BiSheng-WNM firmware version 3.0.0.325 with an exposed and accessible web management interface.
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-supplied firmware patches when available; if no patch exists, isolate affected printers on restricted network segments and implement ingress/egress filtering to prevent exploitation.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48255 — 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-48255 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