CVE-2021-28673
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 Phaser 6510 before 64.61.23 and 64.59.11 (Bridge), WorkCentre 6515 before 65.61.23 and 65.59.11 (Bridge), VersaLink B400 before 37.61.23 and 37.59.01 (Bridge), B405 before 38.61.23 and 38.59.01 (Bridge), B600/B610 before 32.61.23 and 32.59.01 (Bridge), B605/B615 before 33.61.23 and 33.59.01 (Bridge), B7025/30/35 before 58.61.23 and 58.59.11 (Bridge), C400 before 67.61.23 and 67.59.01 (Bridge), C405 before 68.61.23 and 68.59.01 (Bridge), C500/C600 before 61.61.23 and 61.59.01 (Bridge), C505/C605 before 62.61.23 and 62.59.11 (Bridge), C7000 before 56.61.23 and 56.59.01 (Bridge), C7020/25/30 before 57.61.23 and 57.59.01 (Bridge), C8000/C9000 before 70.61.23 and 70.59.01 (Bridge), allows remote attackers with "a weaponized clone file" to execute arbitrary commands in the Web User Interface.
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 · high confidenceMultiple Xerox Phaser, WorkCentre, and VersaLink printer models contain a command injection vulnerability in their Web User Interfaces. Attackers can achieve remote code execution by uploading a 'weaponized clone file' that exploits insufficient input validation during the file cloning/import process. The vulnerability is rated critical due to the trivial exploitability and complete compromise possible via the Web UI.
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< 64.59.11< 64.61.23< 65.59.11< 65.61.23< 37.59.01< 37.61.23< 38.59.01< 38.61.23< 32.59.01< 32.61.23< 32.59.01< 32.61.23< 33.59.01< 33.61.23< 33.59.01< 33.61.23CVSS 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 printer modelAccess the printer Web UI or check the device label to confirm the exact model number (Phaser 6510, Workcentre 6515, Versalink B400, B405, B600, B610, B605, or B615).Affected if The model is one of the eight affected models listed in the CVE.
-
Check the installed firmware versionLog into the Web UI and navigate to the Properties or System Information page to view the current firmware version. Alternatively, print a configuration page from the device menu.Affected if The firmware version is below the patched versions: for Phaser 6510 and Workcentre 6515, below 64.61.23 or 65.61.23 respectively; for Versalink models, below 37.61.23, 38.61.23, or 32.61.23/33.61.23 depending on the specific model.
-
Confirm Web UI is enabledAttempt to access the printer Web UI via a browser at the device IP address (http://[IP]). Verify the login page loads.Affected if The Web User Interface is accessible and responds to requests.
-
Verify file cloning feature accessibilityIn the Web UI, locate the Clone/Import functionality under Configuration, Settings, or Device Settings menus. Determine if this feature is available without administrative credentials.Affected if The file cloning or import feature is present and accessible (with or without authentication).
The environment is affected if the device is one of the eight listed models AND the firmware version is below the patched version thresholds AND the Web UI is accessible with the file cloning feature available.
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 · scoped32.59.0132.61.2333.59.01
Update affected devices to the patched firmware versions specified in the advisory (e.g., 64.61.23 or later for Phaser 6510). If patching is not immediately feasible, disable or restrict access to the Web User Interface and implement network segmentation.
Upgrade to firmware version 64.61.23 or later for Phaser 6510; 65.61.23 or later for WorkCentre 6515; 37.61.23 or later for Versalink B400; 38.61.23 or later for Versalink B405; 32.61.23 or later for Versalink B600/B610; 33.61.23 or later for Versalink B605/B615
- 1. Identify the exact model number and current firmware version of the Xerox device
- 2. Navigate to the Xerox support website (securitydocs.business.xerox.com or xerox.com)
- 3. Locate the firmware download section for the specific device model
- 4. Download the latest firmware version that meets or exceeds the fixed release numbers (64.61.23 or 64.59.11 for Phaser 6510, 65.61.23 or 65.59.11 for WorkCentre 6515, etc.)
- 5. Access the device Web User Interface by entering its IP address in a browser
- 6. Navigate to the System or Settings section and locate the Firmware Update or Software Upgrade option
- 7. Upload the downloaded firmware file and initiate the update process
- 8. Wait for the device to complete the firmware installation and reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28673 — 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-2021-28673 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