CVE-2018-20770
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 · uneditedAn issue was discovered on Xerox WorkCentre 3655, 3655i, 58XX, 58XXi, 59XX, 59XXi, 6655, 6655i, 72XX, 72XXi, 78XX, 78XXi, 7970, 7970i, EC7836, and EC7856 devices before R18-05 073.xxx.0487.15000. There is Blind SQL Injection.
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 confidenceBlind SQL Injection vulnerability in Xerox WorkCentre multifunction printer devices (models 3655, 3655i, 58XX-58XXi, 59XX-59XXi, 6655-6655i, 72XX-72XXi, 78XX-78XXi, 7970-7970i, EC7836, EC7856) before firmware R18-05 073.xxx.0487.15000. The vulnerability is remotely exploitable without authentication and allows attackers to inject malicious SQL queries, potentially exposing sensitive data or compromising the device.
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< 073.060.048.15000< 073.060.048.15000< 073.190.048.15000< 073.190.048.15000< 073.190.048.15000< 073.190.048.15000< 073.190.048.15000< 073.190.048.15000CVSS 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.0/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 WorkCentre modelAccess the device web interface or check the physical label to confirm the exact model number (e.g., 3655, 3655i, 5865, 5875i, etc.)Affected if The model is one of: 3655, 3655i, 58XX-58XXi, 59XX-59XXi, 6655-6655i, 72XX-72XXi, 78XX-78XXi, 7970-7970i, EC7836, EC7856
-
Retrieve the firmware versionLog into the device web interface and navigate to the Properties or About page, or print a configuration page from the device control panel to view the installed firmware version (format: 073.xxx.048.xxxxxx)Affected if The firmware version is below 073.060.048.15000 for 3655/3655i models, or below 073.190.048.15000 for 58XX/58XXi/59XX models, or below 073.xxx.0487.15000 for other affected models
-
Verify management interface exposureCheck if the device web management interface (HTTP/HTTPS on port 80/443) is accessible from untrusted networks by scanning the device IP or reviewing firewall rulesAffected if The web interface is reachable from outside the local network or from untrusted VLANs without access controls
-
Confirm vulnerability is exploitableSend a crafted SQL injection payload to the web login or query parameters (e.g., ' OR '1'='1) and observe if the application returns database-related errors or behaves differently than expectedAffected if The device responds with SQL errors, exhibits unexpected behavior, or allows authentication bypass when injecting SQL syntax into login fields
The environment is affected if the device is a vulnerable WorkCentre model (3655/3655i/58XX-59XX/6655-72XX/78XX/7970/EC7XXX series) AND the firmware version is below the R18-05 threshold (073.xxx.0487.15000) AND the management interface is network-accessible.
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 · scoped073.060.048.15000073.190.048.15000
Apply vendor firmware update R18-05 (073.xxx.0487.15000) or later. If immediate patching is not feasible, restrict network access to the device management interface using network segmentation or firewall rules.
R18-05 firmware (073.xxx.0487.15000 or higher)
- 1. Identify the exact WorkCentre model number from the device front panel or label
- 2. Download the R18-05 firmware update from the official Xerox support website (securitydocs.business.xerox.com) matching your specific model
- 3. Transfer the firmware file to the device via USB or network, following Xerox firmware update instructions
- 4. Initiate the firmware upgrade through the device's web interface (CentreWare) or front panel controls
- 5. Wait for the upgrade to complete and the device to fully reboot - do not power off during this process
- 6. Verify the firmware version has been updated to 073.xxx.0487.15000 or higher after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20770 — 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-2018-20770 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