CVE-2016-11061
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 WorkCentre 3655, 3655i, 58XX, 58XXi, 59XX, 59XXi, 6655, 6655i, 72XX, 72XXi, 78XX, 78XXi, 7970, and 7970i devices before 073.xxx.086.15410 do not properly escape parameters in the support/remoteUI/configrui.php script, which can allow an unauthenticated attacker to execute OS commands on the device.
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 WorkCentre printer models contain an unauthenticated command injection vulnerability in the support/remoteUI/configrui.php script. The script fails to properly escape parameters before passing them to OS command execution, allowing remote attackers to inject and execute arbitrary operating system commands on affected devices.
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.086.15410< 073.060.086.15410< 073.190.086.15410< 073.190.086.15410< 073.190.086.15410< 073.190.086.15410< 073.190.086.15410< 073.190.086.15410CVSS 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 WorkCentre modelAccess the device web interface or check the physical label to determine the exact model number (e.g., Workcentre 3655, 5865, 5875, 5890, or their i variants)Affected if The model is one of: 3655, 3655i, 5865, 5865i, 5875, 5875i, 5890, or 5890i
-
Check the installed firmware versionLog into the web管理界面,导航到设备信息或系统设置页面,查看固件版本信息。或者通过SNMP或设备菜单获取版本号。Affected if The firmware version is below 073.060.086.15410 for 3655/3655i models, or below 073.190.086.15410 for 5865/5865i/5875/5875i/5890/5890i models
-
Verify the vulnerable script is accessibleAttempt to access the URI /support/remoteUI/configrui.php on the device web server using a GET requestAffected if The script returns an HTTP 200 response, indicating it exists and is accessible
-
Confirm web management interface is enabledVerify the device web server is running and reachable on the network by accessing the main page or remoteUI portalAffected if The web interface is exposed and responds to requests, enabling the attack surface for this vulnerability
The device is affected if it is a WorkCentre model from the affected list AND its firmware version is below the fixed thresholds AND the web management interface with the vulnerable script is 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.086.15410073.190.086.15410
Upgrade firmware to version 073.xxx.086.15410 or later. If immediate patching is not feasible, implement network segmentation and firewall rules to restrict access to the device's web management interface.
Xerox WorkCentre firmware 073.060.086.15410 or later (3655/3655i) / 073.190.086.15410 or later (58XX, 58XXi, 59XX, 59XXi)
- Obtain the firmware update from Xerox support (securitydocs.business.xerox.com) or your authorized Xerox reseller
- Access the WorkCentre device web interface or admin console
- Navigate to the firmware update section
- Upload and install firmware version 073.060.086.15410 or later for WorkCentre 3655/3655i models
- Upload and install firmware version 073.190.086.15410 or later for WorkCentre 58XX, 58XXi, 59XX, 59XXi models
- After reboot, verify the firmware version matches the fixed release in the device information panel
- Confirm the vulnerability is remediated by testing that the support/remoteUI/configrui.php endpoint no longer accepts arbitrary command injection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-11061 — 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-2016-11061 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