CVE-2023-26301
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 LaserJet Pro print products are potentially vulnerable to an Elevation of Privilege and/or Information Disclosure related to a lack of authentication with certain endpoints.
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 confidenceAuthentication bypass vulnerability in HP LaserJet Pro printers where certain endpoints lack authentication, potentially allowing unauthenticated attackers to elevate privileges to administrative levels or disclose sensitive device information.
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< 6.12.1.12-202306030312< 6.12.1.12-202306030312< 6.12.1.12-202306030312< 6.12.1.12-202306030312< 6.12.1.12-202306030312< 6.12.1.12-202306030312< 6.12.1.12-202306030312< 6.12.1.12-202306030312CVSS 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 printer modelAccess the printer's embedded web server (EWS) by entering the printer's IP address in a browser, or print a configuration page from the printer control panel to view the model numberAffected if The model number matches HP Color LaserJet Pro 4201 or 4203 with model identifiers 4ra87f, 4ra88f, 4ra89a, 5hh48a, 5hh51a, 5hh52a, 5hh53a, or 5hh59a
-
Check firmware versionIn the printer's EWS, navigate to the General or Information tab to view the firmware version; alternatively, check the configuration page printed from the control panelAffected if The installed firmware version is earlier than 6.12.1.12-202306030312 (for example, 6.10.x.x or earlier)
-
Verify web management interface accessibilityAttempt to access the printer's EWS by navigating to the printer's IP address over HTTP/HTTPS using a web browser without providing credentialsAffected if The EWS login page loads or any device information is displayed without requiring authentication, indicating unauthenticated endpoints may be accessible
-
Assess network exposurePing the printer's IP address from an external network or scan the public-facing IP range for port 80 or 443 open on printer IP addressesAffected if The printer's web management interface is reachable from an untrusted or directly internet-exposed network
You are affected if your HP Color LaserJet Pro 4201/4203 model matches one of the affected identifiers AND the firmware version is below 6.12.1.12-202306030312 AND the web interface is accessible (especially from untrusted networks).
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 · scoped6.12.1.12-202306030312
Apply HP firmware updates for affected LaserJet Pro models and ensure printers are not directly exposed to untrusted networks; implement network segmentation and disable unnecessary remote management interfaces.
Firmware version 6.12.1.12-202306030312 or later for HP Color LaserJet Pro 4201/4203 series
- Identify the exact HP Color LaserJet Pro model number (4201 or 4203 series) and current firmware version from the printer's control panel or web interface
- Navigate to HP Support at support.hp.com and search for the specific printer model
- Locate the firmware download section for the printer
- Download firmware version 6.12.1.12-202306030312 or later
- Access the printer's embedded web server (EWS) by entering the printer's IP address in a web browser
- Navigate to the Firmware Update section in EWS
- Upload and apply the downloaded firmware file
- Wait for the firmware update to complete and the printer to reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26301 — 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-26301 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