CVE-2025-5884
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 · uneditedA vulnerability, which was classified as problematic, was found in Konica Minolta bizhub up to 20250202. This affects an unknown part of the component Display MFP Information List. The manipulation of the argument Model Name leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
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 confidenceCross-site scripting (XSS) vulnerability in the Display MFP Information List component of Konica Minolta bizhub devices (versions up to 20250202). The Model Name parameter is not properly sanitized, allowing injection of malicious scripts via remote HTTP requests.
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<= 2025-02-02CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 device as a Konica Minolta bizhubAccess the device web interface or print a configuration page. Look for Konica Minolta branding and 'bizhub' in the model name. Alternatively, query SNMP for the sysDescr or check the device welcome page.Affected if The device is confirmed to be a Konica Minolta bizhub model.
-
Check the firmware versionIn the bizhub web interface, navigate to the Device Information or Utility page. The firmware version is typically displayed as a date (YYYYMMDD format) or a version number. On the control panel, access System Settings > Device Information > Version. Record the firmware date code.Affected if The firmware date code is 20250202 or earlier.
-
Confirm web services are enabledAccess the bizhub web interface by entering the device IP address in a browser. Verify the login page or public information page loads. Check Web Services settings in the Admin menu.Affected if The HTTP web interface is accessible and responds to requests.
-
Locate the Display MFP Information List featureIn the bizhub web interface, search for 'MFP Information', 'Device List', or 'Display MFP Information List' under Utility, Device Settings, or Network settings. Note whether this page exists and is accessible.Affected if The Display MFP Information List component is present and accessible via the web interface.
-
Verify if Model Name parameter accepts inputIf the Display MFP Information List page is found, attempt to access it and observe if it displays or accepts a Model Name parameter. Check if the page reflects user-supplied or configured model names in the output.Affected if The page exists and displays model information without proper sanitization indicators.
The device is affected if it is a Konica Minolta bizhub with firmware dated 20250202 or earlier and has the web interface with Display MFP Information List component 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.
From vendor dataImplement proper input validation and output encoding for the Model Name parameter. Apply context-appropriate escaping when displaying user-supplied data. Consider implementing Content Security Policy (CSP) headers as defense-in-depth.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5884 — 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-2025-5884 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