CVE-2023-5113
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 · uneditedCertain HP Enterprise LaserJet and HP LaserJet Managed Printers are potentially vulnerable to denial of service due to WS-Print request and potential injections of Cross Site Scripting via jQuery-UI.
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 confidenceHP Enterprise LaserJet and HP LaserJet Managed Printers contain a denial of service vulnerability via WS-Print requests and are susceptible to cross-site scripting through jQuery-UI components. The CVSS 6.1 score indicates moderate severity with network-exploitable DoS and potential authenticated XSS vectors.
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< 5.7CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 printer model and seriesAccess the printer web interface (embedded web server) or check the device physical label to confirm it is an HP Enterprise LaserJet or HP LaserJet Managed modelAffected if The device is an HP Enterprise LaserJet or HP LaserJet Managed printer
-
Check firmware versionNavigate to the printer web interface > General tab > Firmware Version, or print a configuration page from the control panel to view the installed Futuresmart versionAffected if Firmware version is Futuresmart 5 with version below 5.7 (e.g., 5.6.x, 5.5.x)
-
Verify WS-Print service is exposedCheck if port 9100 (RAW printing) or the WS-Print endpoint is accessible from the network. Use a network scanner or check printer network settings > ports > enable WS-Print or RAW printing is turned onAffected if WS-Print service is enabled and accessible on the network (the DoS vector requires this service to be reachable)
-
Check jQuery-UI exposureInspect the printer web interface source code or check if the /jquery-ui/ or similar jQuery-UI paths are accessible via HTTP GET requests to the deviceAffected if The web interface uses jQuery-UI components and is accessible (the XSS vector requires user interaction with these components)
You are affected if you have an HP Enterprise LaserJet or HP LaserJet Managed printer running Futuresmart firmware version below 5.7 with WS-Print service enabled and accessible on the network.
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 data5.7
Apply the latest HP firmware update for affected LaserJet devices and implement input validation/sanitization for jQuery-UI interactions. Consider network segmentation to limit exposure to WS-Print services.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5113 — 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-2023-5113 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