dbcve.org
Workcentre 232Hardware / appliance · Xerox

CVE-2006-6436

MEDIUM · 6.8 CVSS v2.0 Published 2006-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Cross-site scripting (XSS) vulnerability in the Network controller in Xerox WorkCentre and WorkCentre Pro before 12.050.03.000, 13.x before 13.050.03.000, and 14.x before 14.050.03.000 allows remote attackers to inject arbitrary web script or HTML via HTTP TRACE messages.

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 confidence

Cross-site scripting (XSS) vulnerability in the Network controller of Xerox WorkCentre and WorkCentre Pro allows remote attackers to inject arbitrary web script or HTML via HTTP TRACE messages. The vulnerability affects versions before 12.050.03.000, 13.x before 13.050.03.000, and 14.x before 14.050.03.000.

MitigationUpdate Xerox WorkCentre/Pro firmware to version 12.050.03.000, 13.050.03.000, 14.050.03.000 or later. Alternatively, disable HTTP TRACE method at the network perimeter (firewall/proxy) as a compensating control.

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
Workcentre 232Hardware / appliance
Affected:all versions
Workcentre 238Hardware / appliance
Affected:all versions
Workcentre 245Hardware / appliance
Affected:all versions
Workcentre 255Hardware / appliance
Affected:all versions
Workcentre 265Hardware / appliance
Affected:all versions
Workcentre 275Hardware / appliance
Affected:all versions

CVSS 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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device web interface or check the device label/menu to confirm it is a Xerox WorkCentre or WorkCentre Pro. Alternatively, check the SNMP sysDescr or DNS/reverse DNS for 'Xerox' and 'WorkCentre' identifiers.
    Affected if The device is NOT a Xerox WorkCentre or WorkCentre Pro, then it is not affected by this specific CVE.
  2. Determine the firmware version
    Log into the device web interface and navigate to the Properties or About section to view the firmware version. This is typically found under 'Configuration', 'System Settings', or 'Device Information'. Compare the version number to the affected ranges (before 12.050.03.000, 13.x before 13.050.03.000, or 14.x before 14.050.03.000).
    Affected if The firmware version is below 12.050.03.000, or is 13.x below 13.050.03.000, or is 14.x below 14.050.03.000, then the device is likely affected.
  3. Check if Network controller is accessible
    Verify that the embedded web server (Network Controller) is enabled and reachable by accessing the device IP address via HTTP/HTTPS in a browser. The vulnerability exists in the Network controller web interface.
    Affected if The Network controller web interface is accessible and returns a login or status page, then the attack surface exists.
  4. Verify HTTP TRACE method is enabled
    Send an HTTP TRACE request to the device web interface (e.g., using curl -X TRACE http://<device-ip>/ or telnet to port 80 and type 'TRACE / HTTP/1.0' followed by two line breaks). Observe if the server responds with the request headers reflected in the response body.
    Affected if The device responds to HTTP TRACE with reflected headers, the XSS vulnerability via TRACE method is present and exploitable.

A user is affected if they have a Xerox WorkCentre or WorkCentre Pro device with firmware version below 12.050.03.000 (or the specific 13.x/14.x thresholds) AND the Network controller is accessible with HTTP TRACE method enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Xerox WorkCentre/Pro firmware to version 12.050.03.000, 13.050.03.000, 14.050.03.000 or later. Alternatively, disable HTTP TRACE method at the network perimeter (firewall/proxy) as a compensating control.

Fix this in Workcentre 232 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing1.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,270
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,032.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-6436 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-6436 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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