CVE-2022-26572
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 · uneditedXerox ColorQube 8580 was discovered to contain an access control issue which allows attackers to print, view the status, and obtain sensitive information.
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 confidenceThe Xerox ColorQube 8580 printer contains an access control vulnerability that allows unauthenticated attackers to send print jobs, view device status, and access sensitive information via the embedded web server or other network interfaces. The issue stems from improper or missing authentication/authorization checks on certain endpoints.
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 dataall versionsCVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the Xerox ColorQube 8580 on the networkScan the network for devices and check the HTTP response header or the web login page for 'Xerox' and 'ColorQube 8580' identifiers, or check the device's system information page if accessible.Affected if The device is a Xerox ColorQube 8580 printer.
-
Confirm the embedded web server is accessibleAccess the device's IP address via HTTP/HTTPS in a web browser without providing any credentials. Observe whether a login page or device status page loads.Affected if The web interface loads and displays device information or a login prompt without requiring authentication.
-
Test for unauthenticated endpoint accessNavigate to common endpoints such as / or /status.htm (or similar status-related paths) without logging in. Attempt to submit a print job request if the interface allows it without authentication prompts.Affected if Endpoints return device status, configuration, or allow print job submission without any login credentials.
-
Check the firmware versionLocate the firmware version information in the web interface (typically under 'Device Information', 'System Settings', or 'About' sections), or via SNMP queries if available.Affected if The device is a Xerox ColorQube 8580 running any firmware version (all versions are affected per the CVE).
If the Xerox ColorQube 8580 web server is accessible and allows access to device status, print jobs, or sensitive information without requiring authentication, the environment is affected by CVE-2022-26572.
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 firmware updates when available; if no patch exists, implement network segmentation to isolate the printer from untrusted networks and restrict access via firewall rules or ACLs to limit who can communicate with the device.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26572 — 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-26572 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