dbcve.org
Fiery WebtoolsApplication · Xerox

CVE-2009-3913

HIGH · 7.5 CVSS v2.0 Published 2009-11-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
SQL injection vulnerability in summary.php in Xerox Fiery Webtools allows remote attackers to execute arbitrary SQL commands via the select parameter.

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 confidence

SQL injection vulnerability in summary.php in Xerox Fiery Webtools allows remote attackers to execute arbitrary SQL commands via the select parameter. The flaw enables unauthenticated remote attackers to inject malicious SQL queries, potentially leading to unauthorized database access, data exfiltration, or complete system compromise.

MitigationRemediate by implementing parameterized queries or prepared statements in summary.php to properly handle the select parameter input. Additionally, apply input validation and consider network-level access controls to restrict Webtools exposure until the patch is applied.

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
Fiery WebtoolsApplication
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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/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. Determine if Xerox Fiery Webtools is installed and accessible
    Attempt to access the Fiery Webtools interface via HTTP/HTTPS on the device IP or hostname. Common paths include /, /webtools, or /fwstarthtml.jsp. Check for login pages or Fiery-specific branding.
    Affected if Webtools interface responds with Fiery login or status page, indicating the software is running and exposed.
  2. Verify the summary.php endpoint exists
    Send an HTTP GET request to the path /summary.php on the Webtools server. For example: http://[device-ip]/summary.php
    Affected if The server returns a response (200 OK or error page) for summary.php, confirming the vulnerable script is present.
  3. Confirm the select parameter accepts user input
    Send a crafted GET request to summary.php with a test value in the select parameter, such as: /summary.php?select=test. Observe whether the application processes this parameter without rejecting it.
    Affected if The application accepts the select parameter and reflects or processes the input, indicating the parameter is handled without proper sanitization.
  4. Validate SQL injection vulnerability exists
    Send a time-based blind SQL injection test payload in the select parameter, for example: /summary.php?select=1' AND SLEEP(5)--. Measure server response time.
    Affected if The server delays response by approximately 5 seconds or returns a database error, confirming SQL injection is possible.
  5. Assess network exposure of Webtools
    Determine if the Webtools interface is accessible from untrusted networks by reviewing firewall rules, ACLs, or network segmentation around the Fiery device.
    Affected if Webtools is reachable from the internet or untrusted network segments without access controls.

A user is affected if their Fiery Webtools interface is network-accessible and the summary.php endpoint processes the select parameter without sanitization, enabling unauthenticated SQL injection attacks.

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

Remediate by implementing parameterized queries or prepared statements in summary.php to properly handle the select parameter input. Additionally, apply input validation and consider network-level access controls to restrict Webtools exposure until the patch is applied.

Fix this in Fiery Webtools Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-3913 — 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-2009-3913 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